Authenticated server crash via unbounded image dimensions
Published Feb 22, 2024 · Updated Apr 22, 2025
Resource-exhaustion DoS in Apache Answer 1.2.1 and earlier allows remote authenticated users to crash the server via an uploaded image. The content image-upload path processes attacker-controlled pixel dimensions without a documented pixel bound, causing allocation to exhaust server memory. A logged-in account with permission to post image content is required, and successful exploitation interrupts the Answer service.
Summary
What happened
Resource-exhaustion DoS in Apache Answer 1.2.1 and earlier allows remote authenticated users to crash the server via an uploaded image. The content image-upload path processes attacker-controlled pixel dimensions without a documented pixel bound, causing allocation to exhaust server memory. A logged-in account with permission to post image content is required, and successful exploitation interrupts the Answer service.
The record
- CVE
- CVE-2024-22393
- Published
- Feb 22, 2024
- Updated
- Apr 22, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Answer
- Classifications
- CWE-434, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 22, 2024CVE publishedPublication date reported by the CVE source.
- Apr 22, 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 <=1.2.1
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
- Pixel Flood Attack proof of conceptproof of concept · unverified
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