Proxied request alteration via unchecked parser failure
Published Apr 15, 2025 · Updated Apr 15, 2025
Request integrity failure in chimurai http-proxy-middleware before 2.0.9 and 3.x before 3.0.5 allows remote attackers to alter proxied bodies. The fixRequestBody handler reconstructs and writes req.body without checking req.readableLength, so processing continues when bodyParser leaves unread bytes after a parse failure. Exposure requires bodyParser and fixRequestBody on a reachable proxy route; malformed bodies can then change data delivered to the backend.
Summary
What happened
Request integrity failure in chimurai http-proxy-middleware before 2.0.9 and 3.x before 3.0.5 allows remote attackers to alter proxied bodies. The fixRequestBody handler reconstructs and writes req.body without checking req.readableLength, so processing continues when bodyParser leaves unread bytes after a parse failure. Exposure requires bodyParser and fixRequestBody on a reachable proxy route; malformed bodies can then change data delivered to the backend.
The record
- CVE
- CVE-2025-32997
- Published
- Apr 15, 2025
- Updated
- Apr 15, 2025
- Vendor
- Chimurai
- Product
- http-proxy-middleware
- Classifications
- CWE-754, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- Apr 15, 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 <2.0.9
- Affected versionversion=3.0.0 <3.0.5
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