Memory corruption via overflowing XML escape size
Published Mar 14, 2022 · Updated Aug 3, 2024
Integer overflow in Apache HTTP Server 2.4.52 and earlier allows remote attackers to corrupt memory via oversized XML request bodies. The ap_escape_html2 function used int counters while expanding XML body bytes, so a body above 350 MB on a 32-bit build can wrap the calculated output size and drive out-of-bounds writes. Exploitation requires LimitXMLRequestBody to be raised above 350 MB from its 1 MB default; the corruption can crash the service or alter execution.
Summary
What happened
Integer overflow in Apache HTTP Server 2.4.52 and earlier allows remote attackers to corrupt memory via oversized XML request bodies. The ap_escape_html2 function used int counters while expanding XML body bytes, so a body above 350 MB on a 32-bit build can wrap the calculated output size and drive out-of-bounds writes. Exploitation requires LimitXMLRequestBody to be raised above 350 MB from its 1 MB default; the corruption can crash the service or alter execution.
The record
- CVE
- CVE-2022-22721
- Published
- Mar 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-190, CAPEC-92, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 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=Apache HTTP Server 2.4 <=2.4.52
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.
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