Unauthenticated code execution via crafted packet parsing
Published Aug 12, 2021 · Updated Aug 4, 2024
Memory corruption in RCDCAP before 1.0.5 allows remote attackers to execute arbitrary code or crash the application via crafted packets. The public records identify affected packet parsers but do not disclose the parser, malformed field, or unsafe operation that corrupts memory. No authentication or user interaction is required; processing a crafted packet can compromise the process or interrupt capture service.
Summary
What happened
Memory corruption in RCDCAP before 1.0.5 allows remote attackers to execute arbitrary code or crash the application via crafted packets. The public records identify affected packet parsers but do not disclose the parser, malformed field, or unsafe operation that corrupts memory. No authentication or user interaction is required; processing a crafted packet can compromise the process or interrupt capture service.
The record
- CVE
- CVE-2021-37222
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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
No sourced classifications are available.
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