SSRF via unvalidated CRLF header values
Published Nov 4, 2024 · Updated Nov 8, 2024
CRLF injection in ReactiveUI Refit before 7.2.22 allows attackers to trigger SSRF through user-controlled HTTP header values. SetHeader passes attribute-derived names and values to HttpHeaders.TryAddWithoutValidation without removing carriage returns or line feeds. Exposure requires a host application to place attacker-controlled data in Header, HeaderCollection, or Authorize values over HTTP/1.1, enabling request splitting or additional outbound requests.
Summary
What happened
CRLF injection in ReactiveUI Refit before 7.2.22 allows attackers to trigger SSRF through user-controlled HTTP header values. SetHeader passes attribute-derived names and values to HttpHeaders.TryAddWithoutValidation without removing carriage returns or line feeds. Exposure requires a host application to place attacker-controlled data in Header, HeaderCollection, or Authorize values over HTTP/1.1, enabling request splitting or additional outbound requests.
The record
- CVE
- CVE-2024-51501
- Published
- Nov 4, 2024
- Updated
- Nov 8, 2024
- Vendor
- ReactiveUI
- Product
- Refit
- Classifications
- CWE-93
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 8, 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=0 <8.0.0
- Affected versionversion=< 7.2.22
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
- Upstream request-splitting proof of conceptproof of concept · demonstrated
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