Unauthenticated process crash via multipart buffer overflow
Published Aug 25, 2022 · Updated Aug 3, 2024
Buffer overflow in Apache libapreq2 2.16 and earlier allows remote attackers to crash processes via multipart form uploads. The multipart form parser copies attacker-controlled input without checking that it fits the destination buffer; Apache has not identified the function. No authentication or user interaction is required, and the documented consequence is service interruption from a process crash, not code execution.
Summary
What happened
Buffer overflow in Apache libapreq2 2.16 and earlier allows remote attackers to crash processes via multipart form uploads. The multipart form parser copies attacker-controlled input without checking that it fits the destination buffer; Apache has not identified the function. No authentication or user interaction is required, and the documented consequence is service interruption from a process crash, not code execution.
The record
- CVE
- CVE-2022-22728
- Published
- Aug 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- libapreq2
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.16
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