{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26142 exists.","fix":"No fix has been published for CVE-2023-26142 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26142 is a medium-severity vulnerability in Crow, published on 12 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26142 and fix it if it is affected.\n\nWhat it is: CVE-2023-26142 is a medium-severity vulnerability in Crow, published on 12 Sep 2023. 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-2023-26142 exists.\n\nAffected product: Crow. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-26142/ (Markdown: https://insights.sbomify.com/CVE-2023-26142/index.md)","id":"CVE-2023-26142","markdown":"https://insights.sbomify.com/CVE-2023-26142/index.md","name":"CVE-2023-26142","record":{"aliases":["GHSA-3r2p-c9r5-pw6w"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Crow HTTP library","requires_auth":"none","summary":"Attackers can inject malicious content into HTTP responses via CRLF injection in header functions, potentially leading to cache poisoning or XSS.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"crow","vendor":"crowcpp"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"All versions of the package crow are vulnerable to HTTP Response Splitting when untrusted user input is used to build header values. Header values are not properly sanitized against CRLF Injection in the set_header and add_header functions. An attacker can add the \\r\\n (carriage return line feeds) characters to end the HTTP response headers and inject malicious content.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Other in Crow","id":"CVE-2023-26142","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"blamer vulnerable to Arbitrary Argument Injection via the blameByFile() API","id":"CVE-2023-26143"},"packages":[],"prev":{"headline":"sidekiq Denial of Service vulnerability","id":"CVE-2023-26141"},"products":["Crow"],"published":"2023-09-12","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2022-38667","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-34970","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-38668","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":6.5,"headline":"Path Traversal","id":"CVE-2021-23514","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":6.5,"headline":"Content Injection","id":"CVE-2021-23824","kev_date_added":null,"published":"2022-01-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["n/a"]},"summary":"Attackers can inject malicious content into HTTP responses via CRLF injection in header functions, potentially leading to cache poisoning or XSS.","url":"https://insights.sbomify.com/CVE-2023-26142/"}