Heap corruption via unchecked fragment offset
Published May 18, 2023 · Updated Jan 21, 2025
Integer overflow in Meta netconsd before 0.2 allows remote attackers to corrupt heap memory through crafted fragmented packets. The parse_packet function checked the offset-plus-text length but failed to reject an offset at or beyond the total fragment length, allowing the addition to wrap before attacker-controlled data was copied. The unauthenticated UDP listener processes the packet without user interaction, exposing the daemon to a crash or attacker-directed memory modification.
Summary
What happened
Integer overflow in Meta netconsd before 0.2 allows remote attackers to corrupt heap memory through crafted fragmented packets. The parse_packet function checked the offset-plus-text length but failed to reject an offset at or beyond the total fragment length, allowing the addition to wrap before attacker-controlled data was copied. The unauthenticated UDP listener processes the packet without user interaction, exposing the daemon to a crash or attacker-directed memory modification.
The record
- CVE
- CVE-2023-28753
- Published
- May 18, 2023
- Updated
- Jan 21, 2025
- Vendor
- Meta
- Product
- netconsd
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2023CVE publishedPublication date reported by the CVE source.
- Jan 21, 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=0.0 <0.2
What conditions does exploitation require?
What is affected?
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.
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