Remote service crash via crafted TCP packets
Published Jul 28, 2022 · Updated Aug 3, 2024
SimpleNetwork TCP Server at commit 29bc615f0d9910eb2f59aa8dff1f54f0e3af4496 double-frees memory, allowing remote attackers to crash the service. The report localizes the fault to TCPServer packet handling but does not disclose which allocation is released twice or the responsible function. No authentication or user interaction is required; repeated large messages trigger the demonstrated service crash, while code execution is not established.
Summary
What happened
SimpleNetwork TCP Server at commit 29bc615f0d9910eb2f59aa8dff1f54f0e3af4496 double-frees memory, allowing remote attackers to crash the service. The report localizes the fault to TCPServer packet handling but does not disclose which allocation is released twice or the responsible function. No authentication or user interaction is required; repeated large messages trigger the demonstrated service crash, while code execution is not established.
The record
- CVE
- CVE-2022-36234
- Published
- Jul 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Public exploit references
- GitHub issue 22 reproduction procedureproof of concept · demonstrated
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