{"answers":{"affected":"2 open source packages ship an affected version, including Refit.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51501 exists.","fix":"Upgrade Refit to 7.2.22 or later.","what":"CVE-2024-51501 is a critical server-side request forgery vulnerability in reactiveui refit, published on 4 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-51501 and fix it if it is affected.\n\nWhat it is: CVE-2024-51501 is a critical server-side request forgery vulnerability in reactiveui refit, published on 4 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51501 exists.\n\nAffected packages and fixed versions:\n- Refit (NuGet): affected all versions; fixed in 7.2.22\n- Refit (NuGet): affected all versions; fixed in 7.2.22\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-51501/ (Markdown: https://insights.sbomify.com/CVE-2024-51501/index.md)","id":"CVE-2024-51501","markdown":"https://insights.sbomify.com/CVE-2024-51501/index.md","name":"CVE-2024-51501","record":{"aliases":["GHSA-3hxg-fxwm-8gf7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Refit REST library","requires_auth":"none","summary":"Attackers can inject CRLF characters into HTTP headers via Refit attributes, potentially enabling request splitting and Server-Side Request Forgery in consuming applications.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"Refit is an automatic type-safe REST library for .NET Core, Xamarin and .NET The various header-related Refit attributes (Header, HeaderCollection and Authorize) are vulnerable to CRLF injection. The way HTTP headers are added to a request is via the `HttpHeaders.TryAddWithoutValidation` method. This method does not check for CRLF characters in the header value. This 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. If 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. Strictly speaking this is a potential vulnerability in applications using Refit and not in Refit itself. This issue has been addressed in release versions 7.2.22 and 8.0.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CRLF injection in Refit's [Header], [HeaderCollection] and [Authorize] attributes","id":"CVE-2024-51501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Panic Vulnerability in loona-hpack","id":"CVE-2024-51502"},"packages":[{"ecosystem":"NuGet","fixed":["7.2.22"],"introduced":["0"],"last_affected":[],"package":"Refit","purl":null,"source":"GHSA-3hxg-fxwm-8gf7"},{"ecosystem":"NuGet","fixed":["7.2.22"],"introduced":["0"],"last_affected":[],"package":"Refit","purl":"pkg:nuget/Refit","source":"GHSA-3hxg-fxwm-8gf7"}],"prev":{"headline":"Denial of service in firmware","id":"CVE-2024-51500"},"products":["refit"],"published":"2024-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-08","vendors":["reactiveui"]},"summary":"Attackers can inject CRLF characters into HTTP headers via Refit attributes, potentially enabling request splitting and Server-Side Request Forgery in consuming applications.","url":"https://insights.sbomify.com/CVE-2024-51501/"}