Skip to content
Fencer Intel
high 7.1

CVE-2024-53271 json

HTTP/1.1 multiple issues with envoy.reloadable_features.http1_balsa_delay_reset in envoy

published last yr. modified 2mo ago also BIT-envoy-2024-53271 , EUVD-2024-51926 , GHSA-rmm5-h2wv-mg4f

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

Summary

Envoy is a cloud-native high-performance edge/middle/service proxy. In affected versions envoy does not properly handle http 1.1 non-101 1xx responses. This can lead to downstream failures in networked devices. This issue has been addressed in versions 1.31.5 and 1.32.3. Users are advised to upgrade. There are no known workarounds for this issue.

Patch / fix

  • bitnami envoy 1.31.5, 1.32.3
  • envoyproxy envoy 1.31.5, 1.32.3

Is CVE-2024-53271 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

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-53271 updated cvss 7.1

envoy: HTTP/1.1 multiple issues with envoy.reloadable_features.http1_balsa_delay_reset in envoy

  • Red Hat OpenShift Service Mesh 2 openshift-service-mesh/istio-cni-rhel8
    affected: no fix available
  • Red Hat OpenShift Service Mesh 2 openshift-service-mesh/pilot-rhel8, openshift-service-mesh/proxyv2-rhel8, openshift-service-mesh/proxyv2-rhel9
    not affected: vulnerable code not present

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
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-rmm5-h2wv-mg4f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami envoy
>=1.31.0, <1.31.5
>=1.32.0, <1.32.3
1.31.5
1.32.3

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-670 Always-Incorrect Control Flow Implementation

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.