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.
🧩 Analysis chain
🏁 Script executed:
Repository: salimfadhley/dockerized_python_playground
Length of output: 128
🏁 Script executed:
Repository: salimfadhley/dockerized_python_playground
Length of output: 195
🌐 Web query:
uvicorn 0.4.6 security advisory GHSA-33c7-2mpw-hg34 GHSA-f97h-2pfx-f59f PYSEC-2020-150 PYSEC-2020-151💡 Result:
For uvicorn 0.4.6, the following advisories apply (all are aliases to the same underlying issues described below): 1) GHSA-33c7-2mpw-hg34 (alias: CVE-2020-7694; alias: PYSEC-2020-150) - Impact: log injection / ANSI escape sequence injection via crafted request URLs, because the request logger logs the URL after urllib.parse.unquote converts percent-encoded sequences into single characters with special meaning in terminal emulators.[1][2] - Affected versions: OSV lists uvicorn versions including 0.4.6 as affected.[1][3] 2) GHSA-f97h-2pfx-f59f (alias: CVE-2020-7695; <your query’s list includes PYSEC-2020-151, which OSV/NVD link to this HTTP response splitting issue>) - Impact: HTTP response splitting. Uvicorn is vulnerable when CRLF sequences are not escaped in HTTP header values, allowing attackers to inject arbitrary headers or even an arbitrary response body when crafted input is used to construct HTTP headers.[4] - Affected versions: OSV lists uvicorn versions including 0.4.6 as affected (via the CVE-2020-7695 / GHSA-f97h-2pfx-f59f mapping).[4][5] What to do - If you are running uvicorn 0.4.6: upgrade to a version that is fixed for these CVEs. Public guidance for these specific issues indicates they are fixed in uvicorn 0.11.7 (or later): “This is fixed in 0.11.7.”[6]
Citations:
Upgrade
uvicorn==0.4.6insrc/requirements.txtuvicorn==0.4.6is affected by GHSA-33c7-2mpw-hg34 (CVE-2020-7694 / PYSEC-2020-150) and GHSA-f97h-2pfx-f59f (CVE-2020-7695 / PYSEC-2020-151). Upgrade touvicorn>=0.11.7(or later).🤖 Prompt for AI Agents