Skip to content
Fencer Intel
medium —

GHSA-pjjw-qhg8-p2p9 json

aiohttp has vulnerable dependency that is vulnerable to request smuggling

published 2y ago modified 2mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary llhttp 8.1.1 is vulnerable to two request smuggling vulnerabilities. Details have not been disclosed yet, so refer to llhttp for future information. The issue is resolved by using llhttp 9+ (which is included in aiohttp 3.8.6+).

Patch / fix

  • pypi aiohttp 3.8.6

Is GHSA-pjjw-qhg8-p2p9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi aiohttp
<3.8.6
3.8.6

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of aio-libs/aiohttp published their own advisory on GitHub. Reviewed sources take precedence over it.