# CVE-2024-53269: Happy Eyeballs: Validate that additional_address are IP addresses instead of crashing when sorting in envoy

> Attackers can crash the Envoy proxy data plane by providing non-IP addresses in Happy Eyeballs sorting, causing a denial of service.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2024
- **Updated:** 18 Dec 2024
- **Also known as:** BIT-envoy-2024-53269, GHSA-mfqp-7mmj-rm53

## What is CVE-2024-53269?

CVE-2024-53269 is a medium-severity vulnerability in Envoyproxy Envoy, published on 18 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Envoy is a cloud-native high-performance edge/middle/service proxy. When additional address are not ip addresses, then the Happy Eyeballs sorting algorithm will crash in data plane. This issue has been addressed in releases 1.32.2, 1.31.4, and 1.30.8. Users are advised to upgrade. Users unable to upgrade may disable Happy Eyeballs and/or change the IP configuration.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

## Which versions are affected by CVE-2024-53269?

1 open source package ship an affected version, including envoy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `envoy` | Bitnami | From 1.30.0 | 1.30.8, 1.31.4, 1.32.2 |

Products: Envoyproxy Envoy.

## How do I fix CVE-2024-53269?

Upgrade envoy to a fixed version for your release line: 1.30.8, 1.31.4 or 1.32.2.

## Is CVE-2024-53269 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53269 exists.

## Other vulnerabilities in Envoyproxy Envoy

- [CVE-2022-29226](https://insights.sbomify.com/CVE-2022-29226/): Trivial authentication bypass in Envoy (critical 10.0)
- [CVE-2019-18801](https://insights.sbomify.com/CVE-2019-18801/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-18802](https://insights.sbomify.com/CVE-2019-18802/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-35470](https://insights.sbomify.com/CVE-2020-35470/): Information disclosure in n/a (high 8.8)
- [CVE-2024-23324](https://insights.sbomify.com/CVE-2024-23324/): Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53269 and fix it if it is affected.

What it is: CVE-2024-53269 is a medium-severity vulnerability in Envoyproxy Envoy, published on 18 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53269 exists.

Affected packages and fixed versions:
- envoy (Bitnami): affected from 1.30.0; fixed in 1.30.8, 1.31.4, 1.32.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53269/ (Markdown: https://insights.sbomify.com/CVE-2024-53269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53269
- OSV: https://osv.dev/vulnerability/CVE-2024-53269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53269/
Summaries are generated and may contain mistakes; the official description above is the record.