aiohttp: Inconsistent Interpretation of HTTP Requests
CVE-2023-37276 is a high-severity inconsistent interpretation of HTTP requests vulnerability in aiohttp from Aio-libs, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected aiohttp versions: < 3.8.5. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.34% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update aiohttp to 3.8.5 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Aio-libs | aiohttp | < 3.8.5 | Not stated |
| Aio-libs Project | aiohttp | before 3.8.5 | 3.8.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.3 | Medium | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. aiohttp v3.8.4 and earlier are bundled with llhttp v6.0.6. Vulnerable code is used by aiohttp for its HTTP request parser when available which is the default case when installing from a wheel. This vulnerability only affects users of aiohttp as an HTTP server (ie `aiohttp.Application`), you are not affected by this vulnerability if you are using aiohttp as an HTTP client library (ie `aiohttp.ClientSession`). Sending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling. This issue has been addressed in version 3.8.5. Users are advised to upgrade. Users unable to upgrade can reinstall aiohttp using `AIOHTTP_NO_EXTENSIONS=1` as an environment variable to disable the llhttp HTTP request parser implementation. The pure Python implementation isn't vulnerable.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Inconsistent Interpretation of HTTP Requests
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How developers prevent this class of flaw
- Use a web server that employs a strict HTTP parsing procedure, such as Apache.
- Terminate the client session after each request.
More Inconsistent Interpretation of HTTP Requests vulnerabilities (CWE-444)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/aio-libs/aiohttp/security/advisories/GHSA-45c4-8wx5-qw6wExploit, Mitigation
Patches and release notes
Technical write-ups (may include proof of concept)
- hackerone.com/reports/2001873Exploit, Third Party Advisory
Other references
Other vulnerabilities in aiohttp
- 8.7 High severity
- 8.7 High severity
- 8.3 High severity
- 8.2 High severity
- 7.5 High severity
- 8.7 High severity
Recent Inconsistent Interpretation of HTTP Requests vulnerabilities
- 9.4 Critical severity
- 9.1 Critical severity
- 7.3 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.