# CVE-2018-9302: Server-side request forgery in n/a

> Remote attackers can exploit an SSRF vulnerability in Cockpit CMS to read arbitrary files or send traffic to internal hosts via the url parameter.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3cg3-vqjf-x53x

## What is CVE-2018-9302?

CVE-2018-9302 is a critical server-side request forgery vulnerability in n/a, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SSRF (Server Side Request Forgery) in /assets/lib/fuc.js.php in Cockpit 0.4.4 through 0.5.5 allows remote attackers to read arbitrary files or send TCP traffic to intranet hosts via the url parameter. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-14611, which was about version 0.13.0, which (surprisingly) is an earlier version than 0.4.4.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Getcockpit Cockpit.

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

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

## Is CVE-2018-9302 being exploited?

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

Public exploit code:

- Cockpit CMS 0.4.4 < 0.5.5 - Server-Side Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-11471](https://insights.sbomify.com/CVE-2018-11471/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9302 is a critical server-side request forgery vulnerability in n/a, published on 2 May 2018. 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-2018-9302 in the wild and no public exploit code.

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

## Sources

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

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