Unauthenticated response splitting via unsanitized redirect URL
Published Feb 4, 2023 · Updated Aug 5, 2024
HTTP response splitting in TurboGears 1.0.11.10 allows remote attackers to inject response headers through a crafted redirect URL. The redirect() function passes a redirect_path containing carriage-return or newline characters into the Location header without rejecting it. An application must route attacker-controlled input into redirect(); successful exploitation adds headers or response-body text to its HTTP response.
Summary
What happened
HTTP response splitting in TurboGears 1.0.11.10 allows remote attackers to inject response headers through a crafted redirect URL. The redirect() function passes a redirect_path containing carriage-return or newline characters into the Location header without rejecting it. An application must route attacker-controlled input into redirect(); successful exploitation adds headers or response-body text to its HTTP response.
The record
- CVE
- CVE-2019-25101
- Published
- Feb 4, 2023
- Updated
- Aug 5, 2024
- Vendor
- TurboGears Project
- Product
- TurboGears
- Classifications
- CWE-436, CWE-113, CAPEC-34, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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=1.0.11.10
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