{"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-7694 in the wild and no public exploit code.","fix":"Upgrade uvicorn to 0.11.7 or later.","what":"CVE-2020-7694 is a low-severity code injection 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-7694 and fix it if it is affected.\n\nWhat it is: CVE-2020-7694 is a low-severity code injection 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-7694 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-7694/ (Markdown: https://insights.sbomify.com/CVE-2020-7694/index.md)","id":"CVE-2020-7694","markdown":"https://insights.sbomify.com/CVE-2020-7694/index.md","name":"CVE-2020-7694","record":{"aliases":["DEBIAN-CVE-2020-7694","GHSA-33c7-2mpw-hg34","PYSEC-2020-150","SNYK-PYTHON-UVICORN-575560","UBUNTU-CVE-2020-7694"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ASGI server","requires_auth":"none","summary":"Attackers can inject ANSI escape sequences into uvicorn logs via crafted URLs, polluting logs and potentially manipulating terminal emulators.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"uvicorn","vendor":"encode"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"This affects all versions of package uvicorn. The request logger provided by the package is vulnerable to ASNI escape sequence injection. Whenever any HTTP request is received, the default behaviour of uvicorn is to log its details to either the console or a log file. When attackers request crafted URLs with percent-encoded escape sequences, the logging component will log the URL after it's been processed with urllib.parse.unquote, therefore converting any percent-encoded characters into their single-character equivalent, which can have special meaning in terminal emulators. By requesting URLs with crafted paths, attackers can: * Pollute uvicorn's access logs, therefore jeopardising the integrity of such files. * Use ANSI sequence codes to attempt to interact with the terminal emulator that's displaying the logs (either in real time or from a file).","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":"Log Injection","id":"CVE-2020-7694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"HTTP Response Splitting","id":"CVE-2020-7695"},"packages":[{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":null,"source":"GHSA-33c7-2mpw-hg34"},{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":"pkg:pypi/uvicorn","source":"GHSA-33c7-2mpw-hg34"},{"ecosystem":"PyPI","fixed":["0.11.7"],"introduced":["0"],"last_affected":[],"package":"uvicorn","purl":"pkg:pypi/uvicorn","source":"PYSEC-2020-150"}],"prev":{"headline":"Denial of Service (DoS)","id":"CVE-2020-7693"},"products":["uvicorn"],"published":"2020-07-27","related":[{"cvss_score":5.3,"headline":"HTTP Response Splitting","id":"CVE-2020-7695","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 ANSI escape sequences into uvicorn logs via crafted URLs, polluting logs and potentially manipulating terminal emulators.","url":"https://insights.sbomify.com/CVE-2020-7694/"}