# CVE-2018-18358: Server-side request forgery in Chrome

> An attacker on the local network can proxy localhost resources via a crafted WPAD file due to missing localhost special casing in Chrome.

- **Severity:** Medium 5.7 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-18358, GHSA-x2qc-mfcw-3v2v, UBUNTU-CVE-2018-18358

## What is CVE-2018-18358?

CVE-2018-18358 is a medium-severity server-side request forgery vulnerability in Debian Debian Linux, published on 11 Dec 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Lack of special casing of localhost in WPAD files in Google Chrome prior to 71.0.3578.80 allowed an attacker on the local network segment to proxy resources on localhost via a crafted WPAD file.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-18358?

It affects 5 products.


Products: Debian Debian Linux, Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2018-18358?

Upgrade to a fixed version.

## Is CVE-2018-18358 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18358 and fix it if it is affected.

What it is: CVE-2018-18358 is a medium-severity server-side request forgery vulnerability in Debian Debian Linux, published on 11 Dec 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18358 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2018-18358/ (Markdown: https://insights.sbomify.com/CVE-2018-18358/index.md)
```

## Sources

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

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