Application crash via undersized syslog allocation
Published Jan 31, 2024 · Updated Jul 14, 2026
Heap buffer overflow in glibc 2.37 and newer allows remote attackers to crash applications through syslog or vsyslog calls. The __vsyslog_internal function uses a negative snprintf or vsnprintf return value when calculating allocation size, producing a buffer too small for the formatted output. Reachability requires attacker-influenced data to reach an application's logging call and make formatting fail; the grounded consequence is an application crash.
Summary
What happened
Heap buffer overflow in glibc 2.37 and newer allows remote attackers to crash applications through syslog or vsyslog calls. The __vsyslog_internal function uses a negative snprintf or vsnprintf return value when calculating allocation size, producing a buffer too small for the formatted output. Reachability requires attacker-influenced data to reach an application's logging call and make formatting fail; the grounded consequence is an application crash.
The record
- CVE
- CVE-2023-6779
- Published
- Jan 31, 2024
- Updated
- Jul 14, 2026
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-122, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2024CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
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