Vulnerabilities in pkg:nuget/Refit
PACKAGECVE-2024-51501 is a CRITICAL (CVSS 9.8) crlf injection vulnerability (CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')) affecting Refit libraries in the NuGet ecosystem. The issue involves crlf injection in refit's [header], [headercollection] and [authorize] attributes. Remediation is available by upgrading affected packages to version 7.2.22.
pkg:nuget/Refit
Vulnerability advisories affecting package pkg:nuget/Refit. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-3hxg-fxwm-8gf7 | CVE-2024-51501 | CRITICAL | CRLF injection in Refit's [Header], [HeaderCollection] and [Authorize] attributes |
CVE-2024-51501 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2024-51501
To remediate this vulnerability, upgrade all affected Refit dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade Refit to 7.2.22
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for Refit
How to Check if You Are Affected
To determine whether your application is affected by CVE-2024-51501, inspect your project dependencies for Refit:
inspect dependencies for Refit
Analyze the terminal output to locate any version of Refit in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.2.22), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection'), where the product uses crlf (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes crlf sequences from inputs. In Refit, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-51501 Affected Refit Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
Refit
|
NuGet |
< 7.2.22
|
7.2.22
|
References
Frequently Asked Questions
What is CVE-2024-51501?
Which Refit versions are affected?
What version fixes CVE-2024-51501?
Is Refit affected?
What is the CVSS score of CVE-2024-51501?
What CWE is associated with CVE-2024-51501?
How can I check NuGet dependencies for CVE-2024-51501?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3hxg-fxwm-8gf7",
"modified" : "2024-11-08T15:19:17Z",
"published" : "2024-11-04T23:23:17Z",
"aliases" : [ "CVE-2024-51501" ],
"summary" : "CRLF injection in Refit's [Header], [HeaderCollection] and [Authorize] attributes ",
"details" : "### Summary\nThe various header-related Refit attributes (Header, HeaderCollection and Authorize) are vulnerable to CRLF injection.\n\n### Details\nThe way HTTP headers are added to a request is via the `HttpHeaders.TryAddWithoutValidation` method: <https://github.com/reactiveui/refit/blob/258a771f44417c6e48e103ac921fe4786f3c2a1e/Refit/RequestBuilderImplementation.cs#L1328>\nThis method does not check for CRLF characters in the header value.\n\nThis means that any headers added to a refit request are vulnerable to CRLF-injection. In general, CRLF-injection into a HTTP header (when using HTTP/1.1) means that one can inject additional HTTP headers or smuggle whole HTTP requests.\n\n### PoC\nThe below example code creates a console app that takes one command line variable (a bearer token) and then makes a request to some status page with the provided token inserted in the \"Authorization\" header:\n\n```c#\nusing Refit;\n\ninternal class Program\n{\n private static void Main(string[] args)\n {\n // Usage: dotnet run <bearer token> \n string token = args[0];\n var service = RestService.For<IStatusApi>(\"http://insert.some.site.here\");\n string response = service.GetStatus(token).Result;\n Console.WriteLine($\"Response: {response}\");\n }\n\n public interface IStatusApi\n {\n [Get(\"/status\")]\n Task<string> GetStatus([Authorize(\"Bearer\")] string token);\n }\n}\n```\n\nThis application is now vulnerable to CRLF-injection, and can thus be abused to for example perform request splitting and thus server side request forgery (SSRF):\n\n```bash\nanonymous@ubuntu-sofia-672448:~$ dotnet Refit-cli.dll $'test\\r\\nUser-Agent: injected header!\\r\\n\\r\\nGET /smuggled HTTP/1.1\\r\\nHost: insert.some.site.here'\nResponse: <html></html>\n```\n\nThe application intends to send a single request of the form:\n```http\nGET /status HTTP/1.1\nHost: insert.some.site.here\nAuthorization: Bearer <bearer token>\n```\nBut as the application is vulnerable to CRLF injection the above command will instead result in the following two requests being sent:\n```http\nGET /status HTTP/1.1\nHost: insert.some.site.here\nAuthorization: Bearer test\nUser-Agent: injected header!\n```\nand\n```http\nGET /smuggled HTTP/1.1\nHost: insert.some.site.here\n```\n\nThis can be confirmed by checking the access logs on the server where these commands were run (with `insert.some.site.here` pointing to localhost):\n```bash\nanonymous@ubuntu-sofia-672448:~$ sudo tail /var/log/apache2/access.log\n127.0.0.1 - - [29/Aug/2024:12:17:34 +0000] \"GET /status HTTP/1.1\" 200 240 \"-\" \"injected header!\"\n127.0.0.1 - - [29/Aug/2024:12:17:34 +0000] \"GET /smuggled HTTP/1.1\" 404 436 \"-\" \"-\"\n```\n\n### Impact\nIf an application using the Refit library passes a user-controllable value through to a header, then that application becomes vulnerable to CRLF-injection. This is not necessarily a security issue for a command line application like the one above, but if such code were present in a web application then it becomes vulnerable to request splitting (as shown in the PoC) and thus Server Side Request Forgery.\n\nStrictly speaking this is a potential vulnerability in applications using Refit, not in Refit itself, but I would argue that at the very least there needs to be a warning about this behaviour in the Refit documentation.\n\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "NuGet",
"name" : "Refit"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "7.2.22"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/reactiveui/refit/security/advisories/GHSA-3hxg-fxwm-8gf7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-51501"
}, {
"type" : "WEB",
"url" : "https://github.com/reactiveui/refit/commit/483b1d8df18098f137ca0eca056b7e9ec19f70dd"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/reactiveui/refit"
}, {
"type" : "WEB",
"url" : "https://github.com/reactiveui/refit/blob/258a771f44417c6e48e103ac921fe4786f3c2a1e/Refit/RequestBuilderImplementation.cs#L1328"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-93" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2024-11-04T23:23:17Z",
"nvd_published_at" : "2024-11-04T23:15:04Z"
}
}