CVE-2019-9187 json
ikiwiki before 3.20170111.1 and 3.2018x and 3.2019x before 3.20190228 allows SSRF via the aggregate plugin.
published 2019-06-05 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-18564
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- ikiwiki ikiwiki 3.20170111.1, 3.20190226
- ikiwiki Debian 14, Debian 13, Debian 12 3.20190228-1
debian advisories DEBIAN-CVE-2019-9187
- ikiwiki openSUSE Tumbleweed 3.20200202.3-2.7
opensuse advisories openSUSE-SU-2024:10860-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-9187 updated cvss 5.4
ikiwiki: server-side request forgery resulting in dos
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.70% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
ikiwiki.info
/news/
vendor-advisory
-
lists.debian.org
/debian-lts-announce/2019/03/msg00018.html
mailing-list
- ikiwiki.info /news/version_3.20190228/
Sources
- CVE List CVE-2019-9187
- NVD CVE-2019-9187
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.