Skip to content
Fencer Intel
high 8.1

CVE-2023-27493 json

Envoy doesn't escape HTTP header values

published 3y ago modified 2mo ago also BIT-envoy-2023-27493 , EUVD-2023-31258 , GHSA-w5w5-487h-qv8q

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

Summary

Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, Envoy does not sanitize or escape request properties when generating request headers. This can lead to characters that are illegal in header values to be sent to the upstream service. In the worst case, it can cause upstream service to interpret the original request as two pipelined requests, possibly bypassing the intent of Envoy’s security policy. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. As a workaround, disable adding request headers based on the downstream request properties, such as downstream certificate properties.

Patch / fix

  • bitnami envoy 1.22.9, 1.23.6, 1.24.4, 1.25.3
  • envoyproxy envoy 1.22.9, 1.23.6, 1.24.4, 1.25.3

Is CVE-2023-27493 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-2023-27493 updated cvss 8.1

envoy: envoy doesn't escape HTTP header values

  • Red Hat OpenShift Service Mesh 2.1 servicemesh-proxy, servicemesh-proxy-wasm
    affected: no fix available
  • Red Hat RHOSSM 2.2 for RHEL 8 openshift-service-mesh/proxyv2-rhel8 2.2.9-2
    fixed: vendor fix RHSA-2023:4623
  • Red Hat RHOSSM 2.2 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.2.9-1, openshift-service-mesh/grafana-rhel8 2.2.9-1, openshift-service-mesh/istio-cni-rhel8 2.2.9-1, openshift-service-mesh/ratelimit-rhel8 2.2.9-1, openshift-service-mesh/prometheus-rhel8 2.2.9-1, openshift-service-mesh/istio-must-gather-rhel8 2.2.9-2
    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
total
Assessed
last yr.

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5w5-487h-qv8q referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami envoy
<1.22.9
>=1.23.0, <1.23.6
>=1.24.0, <1.24.4
>=1.25.0, <1.25.3
1.22.9
1.23.6
1.24.4
1.25.3

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-20 Improper Input Validation
  • 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.