Lucene search

GitHub_MVULNRICHMENT:CVE-2024-32475

HistoryApr 18, 2024 - 2:18 p.m.

CVE-2024-32475 Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes

2024-04-1814:18:18

CWE-253

CWE-617

GitHub_M

github.com

cve-2024-32475

envoy

release_assert

auto_sni

:authority header

abnormal termination

tls cluster

sni length

outbound connection

vulnerability

fix

1.30.1

1.29.4

1.28.3

1.27.5

CVSS3

7.5

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

AI Score

6.6

Confidence

Low

SSVC

Exploitation

none

Automatable

yes

Technical Impact

partial

JSON

Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with auto_sni enabled, a request containing a host/:authority header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the host/:authority header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.

ADP Affected

[
  {
    "cpes": [
      "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*"
    ],
    "vendor": "envoyproxy",
    "product": "envoy",
    "versions": [
      {
        "status": "affected",
        "version": "1.13.0",
        "lessThan": "1.27.5",
        "versionType": "semver"
      }
    ],
    "defaultStatus": "unknown"
  }
]