Receiver crash via oversized octet-count prefix
Published May 5, 2022 · Updated Apr 23, 2025
Heap buffer overflow in rsyslog before 8.2204.1 allows remote attackers to crash TCP syslog receivers via octet-counted framing. The octet-count parser keeps writing frame-length digits into a heap buffer after the maximum count is exceeded, allowing adjacent heap data to be corrupted. The affected imtcp, imptcp, imhttp, imgssapi, and imdiag modules accept this framing; receivers enable it by default, but senders must select it.
Summary
What happened
Heap buffer overflow in rsyslog before 8.2204.1 allows remote attackers to crash TCP syslog receivers via octet-counted framing. The octet-count parser keeps writing frame-length digits into a heap buffer after the maximum count is exceeded, allowing adjacent heap data to be corrupted. The affected imtcp, imptcp, imhttp, imgssapi, and imdiag modules accept this framing; receivers enable it by default, but senders must select it.
The record
- CVE
- CVE-2022-24903
- Published
- May 5, 2022
- Updated
- Apr 23, 2025
- Vendor
- rsyslog
- Product
- rsyslog
- Classifications
- CWE-118, CWE-120, CWE-1284, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 5, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.2204.1
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