cve.bz

CVE-2017-18638 graphite project graphite: SSRF

7.5 highExploit referenceEPSS 15%Fix available

High (7.5) in graphite project graphite. EPSS 15% estimated probability of exploitation activity in the next 30 days. Fixed in graphite-web 1.1.6.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
15% (unchanged from 15% a week ago; 15% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-18638 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-18638?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-18638?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-18638 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
graphite_project:graphitethrough 1.1.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vfj6-275q-4pvmPyPIgraphite-web<1.1.61.1.6
PYSEC-2019-151PyPIgraphite-web<1.1.61.1.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian8graphite-web0.9.12+debian-6+deb8u1DLA-1962-1
Debian12, 13, 14graphite-web1.1.4-5DEBIAN-CVE-2017-18638
Ubuntu20.04:LTSgraphite-web1.1.4-5ubuntu0.1USN-6243-1
Ubuntu22.04:LTSgraphite-web1.1.8-1ubuntu0.22.04.1USN-6243-1
UbuntuPro:14.04:LTSgraphite-web0.9.12+debian-3ubuntu0.1~esm1UBUNTU-CVE-2017-18638 USN-6243-1
UbuntuPro:16.04:LTSgraphite-web0.9.15+debian-1ubuntu0.1~esm1UBUNTU-CVE-2017-18638 USN-6243-1
UbuntuPro:18.04:LTSgraphite-web1.0.2+debian-2ubuntu0.1~esm1UBUNTU-CVE-2017-18638 USN-6243-1
SUSEEnterprise Storage 4graphite-web0.9.12-5.3.1SUSE-SU-2019:2803-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Graphite metrics / telemetry data does not contain any sensitive information and hence this flaw is rated as Moderate.

ProductPackageStateAdvisory
Red Hat Ceph Storage 2graphite-webOut of support scope
Red Hat Ceph Storage 3graphite-webOut of support scope
Red Hat Storage 3graphite-webWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-18638.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON