Response splitting via null-prefixed CRLF bypass
Published Feb 4, 2025 · Updated May 23, 2025
HTTP response splitting in Yuji Hirose cpp-httplib 0.17.3 through 0.18.3 allows remote attackers to inject response headers. Request::set_header, Response::set_header, and Response::set_redirect accept null-prefixed CRLF sequences because the prior has_crlf validation misses them. Exploitation requires an embedding application to pass attacker-controlled data to these operations, enabling altered responses or script execution in a recipient browser.
Summary
What happened
HTTP response splitting in Yuji Hirose cpp-httplib 0.17.3 through 0.18.3 allows remote attackers to inject response headers. Request::set_header, Response::set_header, and Response::set_redirect accept null-prefixed CRLF sequences because the prior has_crlf validation misses them. Exploitation requires an embedding application to pass attacker-controlled data to these operations, enabling altered responses or script execution in a recipient browser.
The record
- CVE
- CVE-2025-0825
- Published
- Feb 4, 2025
- Updated
- May 23, 2025
- Vendor
- Yuji Hirose
- Product
- cpp-httplib
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=v0.17.3 <=v0.18.3
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