HighGHSA-33c7-2mpw-hg34CVE-2020-7694PYSEC-2020-150SNYK-PYTHON-UVICORN-575560

Log injection in uvicorn

Published 29 Jul 2020 · Updated 18 Nov 2024

Is your project on an affected uvicorn?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<0.11.7
Fixed in
0.11.7
Update to the fixed version for your release line, for example:pip install 'uvicorn>=0.11.7'

Details

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).

Is GHSA-33c7-2mpw-hg34 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected uvicorn, and gives you the command that fixes it.

More advisories for uvicorn

  • HighCVE-2020-7695HTTP response splitting in uvicorn · 29 Jul 2020
uvicorn security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.