Skip to content
Fencer Vulns
high 8.2

CVE-2024-2653 in the critical feed json

CVE-2024-2653

published 2024-04-03 2 y ago modified 2026-07-08 4 mo ago also GHSA-qjfw-cvjf-f4fm , EUVD-2024-1280

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
80.3%
EPSS 80.3% chance of exploitation in 30 days, percentile 99.6%
public exploits
0
none known

Summary

amphp/http will collect CONTINUATION frames in an unbounded buffer and will not check a limit until it has received the set END_HEADERS flag, resulting in an OOM crash.

Patch / fix

  • packagist amphp/http 1.7.3, 2.1.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-2653 updated cvss 7.5

amphp: CONTINUATION frames DoS

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

80.26% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
GitHub 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Affected packages

ecosystem package affected fixed in
packagist amphp/http
>=2.0.0, <2.1.1
<1.7.3
2.1.1
1.7.3
packagist amphp/http-client
>=4.0.0-rc10, <=4.0.0
 no fix listed

Affected products

  • AMPHP amphp/http-client
  • AMPHP amphp/http
  • amphp http-client
  • amphp http

References

Sources

Fencer Vulns 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.