CVE-2017-18638 in the critical feed json
graphite.composer.views.send_email vulnerable to SSRF
published 2019-10-11 7 y ago modified 2026-07-08 4 mo ago also GHSA-vfj6-275q-4pvm , PYSEC-2019-151 , EUVD-2019-0058
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.3%
- EPSS 15.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
send_email in graphite-web/webapp/graphite/composer/views.py in Graphite through 1.1.5 is vulnerable to SSRF. The vulnerable SSRF endpoint can be used by an attacker to have the Graphite web server request any resource. The response to this SSRF request is encoded into an image file and then sent to an e-mail address that can be supplied by the attacker. Thus, an attacker can exfiltrate any information.
Patch / fix
- pypi graphite-web 1.1.6
- graphite-web Debian 14, Debian 13, Debian 12 1.1.4-5
debian advisories DEBIAN-CVE-2017-18638
- graphite-web Ubuntu Pro 14.04 LTS 0.9.12+debian-3ubuntu0.1~esm1
- graphite-web Ubuntu Pro 16.04 LTS 0.9.15+debian-1ubuntu0.1~esm1
- graphite-web Ubuntu Pro 18.04 LTS 1.0.2+debian-2ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2017-18638
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- graphite-web Enterprise Storage 4 0.9.12-5.3.1
suse advisories SUSE-SU-2019:2803-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-2017-18638 updated cvss 7.5
graphite-web: graphite.composer.views.send_email vulnerable to SSRF
-
Red Hat Ceph Storage 2 graphite-web Red Hat Ceph Storage 3 graphite-webaffected: no fix planned “Out of support scope”
-
Red Hat Storage 3 graphite-webaffected: no fix planned “Will not fix”
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
15.30% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Graphite <=1.1.5 - Server-Side Request Forgery nuclei detection template
- blog.orange.tw https://blog.orange.tw/2017/07/how-i-chained-4-vulnerabilities-on.html#second-bug-internal-graphite-ssrf referenced PoC, tagged "exploit" by a source, unverified
- youtube.com https://www.youtube.com/watch?v=ds4Gp4xoaeA referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/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 |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | graphite-web | <1.1.6 |
1.1.6 |
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/graphite-project/graphite-web/pull/2499
web, third-party-advisory
-
github.com
/graphite-project/graphite-web/commit/71726a0e41a5263f49b973a7b856505a5b931c1f
web
-
blog.orange.tw
/2017/07/how-i-chained-4-vulnerabilities-on.html#second-bug-internal-graphite-ssrf
web, exploit, mitigation, third-party-advisory, article
-
youtube.com
/watch?v=ds4Gp4xoaeA
web, exploit, third-party-advisory
-
github.com
/graphite-project/graphite-web/security/advisories/GHSA-vfj6-275q-4pvm
web, broken-link, advisory
-
github.com
/graphite-project/graphite-web/issues/2008
web, third-party-advisory, report
-
lists.debian.org
/debian-lts-announce/2019/10/msg00030.html
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2017-18638
advisory
-
github.com
/graphite-project/graphite-web
package
-
github.com
/pypa/advisory-database/tree/main/vulns/graphite-web/PYSEC-2019-151.yaml
web
Sources
- CVE List CVE-2017-18638
- GitHub Advisory GHSA-vfj6-275q-4pvm
- NVD CVE-2017-18638
- OSV PYSEC-2019-151
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.