Clusterlabs Libqb
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Clusterlabs Libqb.
By the Year
In 2026 there have been 0 vulnerabilities in Clusterlabs Libqb. Libqb did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 1 | 9.80 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 0.00 |
It may take a day or so for new Libqb vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Clusterlabs Libqb Security Vulnerabilities
libqb <2.0.8: Buffer Overflow via long log messages in log_blackbox.c
CVE-2023-39976
9.8 - Critical
- August 08, 2023
log_blackbox.c in libqb before 2.0.8 allows a buffer overflow via long log messages because the header size is not considered.
Classic Buffer Overflow
libqb before 1.0.5 allows local users to overwrite arbitrary files via a symlink attack
CVE-2019-12779
- June 07, 2019
libqb before 1.0.5 allows local users to overwrite arbitrary files via a symlink attack, because it uses predictable filenames (under /dev/shm and /tmp) without O_EXCL.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Clusterlabs Libqb or by Clusterlabs? Click the Watch button to subscribe.
