{"answers":{"affected":"3 open source packages ship an affected version, including uvicorn. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7695 in the wild and no public exploit code.","fix":"Upgrade uvicorn to 0.11.7 or later.","what":"CVE-2020-7695 is a medium-severity vulnerability in uvicorn, published on 27 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7695 and fix it if it is affected.\n\nWhat it is: CVE-2020-7695 is a medium-severity vulnerability in uvicorn, published on 27 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7695 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- uvicorn (PyPI): affected all versions; fixed in 0.11.7\n- uvicorn (PyPI): affected all versions; fixed in 0.11.7\n- uvicorn (PyPI): affected all versions; fixed in 0.11.7\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-2020-7695/ (Markdown: https://insights.sbomify.com/CVE-2020-7695/index.md)","id":"CVE-2020-7695","markdown":"https://insights.sbomify.com/CVE-2020-7695/index.md","name":"CVE-2020-7695","record":{"aliases":["DEBIAN-CVE-2020-7695","GHSA-f97h-2pfx-f59f","PYSEC-2020-151","SNYK-PYTHON-UVICORN-570471","UBUNTU-CVE-2020-7695"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ASGI server","requires_auth":"none","summary":"Attackers can inject arbitrary headers or response bodies via CRLF injection in Uvicorn, 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":"uvicorn","vendor":"encode"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HTTP Response Splitting","id":"CVE-2020-7695","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"other","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"Information Exposure","id":"CVE-2020-7696"},"packages":[{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":null,"source":"GHSA-f97h-2pfx-f59f"},{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":"pkg:pypi/uvicorn","source":"GHSA-f97h-2pfx-f59f"},{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":"pkg:pypi/uvicorn","source":"PYSEC-2020-151"}],"prev":{"headline":"Log Injection","id":"CVE-2020-7694"},"products":["uvicorn"],"published":"2020-07-27","related":[{"cvss_score":3.7,"headline":"Log Injection","id":"CVE-2020-7694","kev_date_added":null,"published":"2020-07-27"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can inject arbitrary headers or response bodies via CRLF injection in Uvicorn, potentially leading to cache poisoning or XSS.","url":"https://insights.sbomify.com/CVE-2020-7695/"}