# CVE-2020-25018: Other in n/a

> Envoy proxy may fail to parse request URLs requiring host canonicalization, potentially leading to service disruption.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwwh-fc9w-9673

## What is CVE-2020-25018?

CVE-2020-25018 is a high-severity vulnerability in Envoyproxy Envoy, published on 1 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization.

## Which versions are affected by CVE-2020-25018?

It affects 1 product.


Products: Envoyproxy Envoy.

## How do I fix CVE-2020-25018?

No fix has been published for CVE-2020-25018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25018 being exploited?

There is no known exploitation of CVE-2020-25018 in the wild and no public exploit code.

## 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-2020-25018 and fix it if it is affected.

What it is: CVE-2020-25018 is a high-severity vulnerability in Envoyproxy Envoy, published on 1 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25018 in the wild and no public exploit code.

Affected product: Envoyproxy Envoy. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2020-25018/ (Markdown: https://insights.sbomify.com/CVE-2020-25018/index.md)
```

## Sources

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

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