CVE-2024-23325
Assigner: GitHub_M
Published: 2024-02-09T22:47:13.048Z
State: PUBLISHED
title: Envoy crashes when using an address type that isn’t supported by the OS
problemTypes: descriptions: cweId: CWE-755
description: CWE-755: Improper Handling of Exceptional Conditions
type: CWE
descriptions: cweId: CWE-248
description: CWE-248: Uncaught Exception
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
version: 3.1
affected: vendor: envoyproxy
product: envoy
versions: version: >= 1.29.0, < 1.29.1
status: affected
version: >= 1.28.0, < 1.28.1
status: affected
version: >= 1.27.0, < 1.27.3
status: affected
version: < 1.26.7
status: affected
descriptions: value: Envoy is a high-performance edge/middle/service proxy. Envoy crashes in Proxy protocol when using an address type that isn’t supported by the OS. Envoy is susceptible to crashing on a host with IPv6 disabled and a listener config with proxy protocol enabled when it receives a request where the client presents its IPv6 address.  It is valid for a client to present its IPv6 address to a target server even though the whole chain is connected via IPv4. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
source: advisory: GHSA-5m7c-mrwr-pm26
discovery: UNKNOWN