HTTP::Parser::XS versions before 0.18 for Perl truncate PATH_INFO at an encoded NUL byte in parse_http_request
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.18
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The HTTP::Parser::XS Perl module, which parses HTTP requests using its XS (C-based) backend, is affected; the pure-Perl backend is not. The flaw can cause the request path to be cut short at an encoded NUL byte, so a proxy or filter may inspect a different path than the one the application ultimately routes on.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
HTTP::Parser::XS versions before 0.18 for Perl truncate PATH_INFO at an encoded NUL byte in parse_http_request. The XS parser URL-decodes the request path and measures the result with strlen(), so PATH_INFO ends at the first byte decoded from %00. The pure-Perl backend is not affected. A remote attacker can send a path that a proxy or filter checks in full while the application routes on a shorter one.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- HTTP-Parser-XS
fixed in 0.18