# CVE-2019-9187: Server-side request forgery in n/a

> Attackers can exploit Server-Side Request Forgery in the aggregate plugin to read local files and access internal resources.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-9187, DLA-1716-1, DSA-4399-1, GHSA-3h26-q9xc-fjff, UBUNTU-CVE-2019-9187

## What is CVE-2019-9187?

CVE-2019-9187 is a high-severity server-side request forgery vulnerability in n/a, published on 5 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ikiwiki before 3.20170111.1 and 3.2018x and 3.2019x before 3.20190228 allows SSRF via the aggregate plugin. The impact also includes reading local files via file: URIs.

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

## Which versions are affected by CVE-2019-9187?

It affects 1 product.


Products: Ikiwiki Ikiwiki.

## How do I fix CVE-2019-9187?

Upgrade to a fixed version.

## Is CVE-2019-9187 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10026](https://insights.sbomify.com/CVE-2016-10026/): Missing authorization in n/a (high 7.5)
- [CVE-2008-0169](https://insights.sbomify.com/CVE-2008-0169/): Auth bypass in n/a (medium 6.8)
- [CVE-2016-9645](https://insights.sbomify.com/CVE-2016-9645/): Editing restriction bypass for git revert (medium 6.5)
- [CVE-2010-1673](https://insights.sbomify.com/CVE-2010-1673/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2011-0428](https://insights.sbomify.com/CVE-2011-0428/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9187 and fix it if it is affected.

What it is: CVE-2019-9187 is a high-severity server-side request forgery vulnerability in n/a, published on 5 Jun 2019. 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-2019-9187 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-2019-9187/ (Markdown: https://insights.sbomify.com/CVE-2019-9187/index.md)
```

## Sources

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

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