Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π Security & Privacy | π Major | β‘ Quick win
π§© Analysis chain
π Script executed:
Repository: salimfadhley/dockerized_python_playground
Length of output: 489
π Web query:
UVSec PYSEC-2020-150 Uvicorn 0.4.6 log injection HTTP response splitting affected fixed versionπ‘ Result:
The vulnerability identified as PYSEC-2020-150 (also tracked as CVE-2020-7694 and GHSA-33c7-2mpw-hg34) is a log injection vulnerability affecting Uvicorn [1][2][3]. This vulnerability exists because the Uvicorn request logger processes URLs with urllib.parse.unquote before logging them, which converts percent-encoded characters into their single-character equivalents [1][4]. Attackers can exploit this by sending crafted URLs containing ANSI escape sequences or characters that mimic log entries, allowing them to pollute logs or potentially interact with the terminal emulator displaying the logs [1][2][4]. Version 0.4.6 of Uvicorn is affected by this vulnerability [1][5]. The issue was addressed and fixed in Uvicorn version 0.11.7 [2][6][4]. Users running version 0.4.6 or any version earlier than 0.11.7 are advised to upgrade to 0.11.7 or higher to mitigate this risk [4].
Citations:
Upgrade the vulnerable Uvicorn pin before merging.
uvicorn==0.4.6insrc/requirements.txtis affected by log-injection and HTTP-response-splitting advisoryPYSEC-2020-150; the issue is fixed starting with0.11.7. Upgrade it to a secure, FastAPI-compatible release and regenerate the dependency scan.π§° Tools
πͺ OSV Scanner (2.4.0)
[HIGH] 1-1: uvicorn 0.4.6: undefined
(PYSEC-2020-150)
[HIGH] 1-1: uvicorn 0.4.6: undefined
(PYSEC-2020-151)
[HIGH] 1-1: uvicorn 0.4.6: Log injection in uvicorn
(GHSA-33c7-2mpw-hg34)
[HIGH] 1-1: uvicorn 0.4.6: HTTP response splitting in uvicorn
(GHSA-f97h-2pfx-f59f)
π€ Prompt for AI Agents
Source: Linters/SAST tools