Memory corruption via oversized black-box log messages
Published Aug 8, 2023 · Updated Oct 15, 2024
Buffer overflow in libqb before 2.0.8 allows attackers to corrupt memory via an oversized message sent to the black-box logger. In _blackbox_vlogger, qb_vsnprintf_serialize uses the full buffer size for the formatted message without reserving actual_size bytes for the log header. Exploitation requires a consuming application to pass attacker-controlled, overlong content into black-box logging; the documented result is memory corruption, while code execution is not established.
Summary
What happened
Buffer overflow in libqb before 2.0.8 allows attackers to corrupt memory via an oversized message sent to the black-box logger. In _blackbox_vlogger, qb_vsnprintf_serialize uses the full buffer size for the formatted message without reserving actual_size bytes for the log header. Exploitation requires a consuming application to pass attacker-controlled, overlong content into black-box logging; the documented result is memory corruption, while code execution is not established.
The record
- CVE
- CVE-2023-39976
- Published
- Aug 8, 2023
- Updated
- Oct 15, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Oct 15, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo