Request smuggling via divergent Content-Length parsing
Published Jun 27, 2022 · Updated Apr 22, 2025
HTTP request smuggling in libwww-perl HTTP::Daemon before 6.15 allows remote attackers to access protected APIs or poison caches. get_request accepts multiple Content-Length values without requiring every value to be numeric and identical, so HTTP agents can disagree on request boundaries. Exposure requires an application to serve requests through this Perl class, which is commonly used for local development and testing.
Summary
What happened
HTTP request smuggling in libwww-perl HTTP::Daemon before 6.15 allows remote attackers to access protected APIs or poison caches. get_request accepts multiple Content-Length values without requiring every value to be numeric and identical, so HTTP agents can disagree on request boundaries. Exposure requires an application to serve requests through this Perl class, which is commonly used for local development and testing.
The record
- CVE
- CVE-2022-31081
- Published
- Jun 27, 2022
- Updated
- Apr 22, 2025
- Vendor
- libwww-perl
- Product
- HTTP::Daemon
- Classifications
- CWE-444, CAPEC-33, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2022CVE 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=< 6.15
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