6.5

CVE-2023-47641: Inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding` in aiohttp

Modified
AliasesSUSE-SU-2023:4909-1GHSA-xx9p-xxvh-7g8jPYSEC-2023-247
Published 14-11-2023Last modified 03-11-2025

Vulnerability summary

CVE-2023-47641 is a medium (CVSS 6.5) vulnerability in aio-libs aiohttp. EPSS estimates a 0.83% chance of exploitation in the next 30 days, higher than 57.7% of scored vulnerabilities. 1 public exploit is recorded.

Priority
Routine

Not severe (CVSS 3.4, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
6.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.83%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits1github

Advisory lineage

Upstream 0 · Downstream 4 · Related 3

Timeline

  1. 14-11-2023
    PublishedVulnerability first disclosed.
  2. 03-11-2025
    Last modifiedVulnerability information updated.

Description

aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. Affected versions of aiohttp have a security vulnerability regarding the inconsistent interpretation of the http protocol. HTTP/1.1 is a persistent protocol, if both Content-Length(CL) and Transfer-Encoding(TE) header values are present it can lead to incorrect interpretation of two entities that parse the HTTP and we can poison other sockets with this incorrect interpretation. A possible Proof-of-Concept (POC) would be a configuration with a reverse proxy(frontend) that accepts both CL and TE headers and aiohttp as backend. As aiohttp parses anything with chunked, we can pass a chunked123 as TE, the frontend entity will ignore this header and will parse Content-Length. The impact of this vulnerability is that it is possible to bypass any proxy rule, poisoning sockets to other users like passing Authentication Headers, also if it is present an Open Redirect an attacker could combine it to redirect random users to another website and log the request. This vulnerability has been addressed in release 3.8.0 of aiohttp. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS metrics

5 scores · 5 sources · 1 version

EPSS trend

Probability

0.83%

Chance of exploitation in the next 30 days

Percentile

58%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.83% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

1 found
  • githubUnverified

    Aiohttp

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, user interaction (CVSS vector). Other conditions: not stated in public data.

Suse5 products
  • python-aiohttp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP1< 3.6.0-150100.3.12.1
  • python-aiohttp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP2< 3.6.0-150100.3.12.1
  • python-aiohttp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP3< 3.6.0-150100.3.12.1
  • python-aiohttp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP4< 3.6.0-150100.3.12.1
  • python-aiohttp&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP5< 3.6.0-150100.3.12.1
Opensuse2 products
  • python-aiohttp&distro=openSUSE Leap 15.4< 3.6.0-150100.3.12.1
  • python-aiohttp&distro=openSUSE Leap 15.5< 3.6.0-150100.3.12.1
Aio-libs1 product
Aiohttp1 product
Debian1 product
  • python-aiohttp< 3.8.1-1
PyPI1 product
  • aiohttp< f016f0680e4ace6742b03a70cb0382ce86abe371 | < 3.8.0
Ubuntu1 product
  • python-aiohttpAll versions (No fix recorded)

7 vendors · 12 products

References

13 links
Show all 13 references