Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2017-18638

SSRF (Server-Side Request Forgery) in graphite-web (CVE-2017-18638)

Summary

SSRF in graphite-web (CVE-2017-18638). Confidential information can be exposed externally. Exploitable via send_email. Mitigation: upgrade to 1.1.6 or later.

Original description

The description as published by the source.

Impact

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. Email will be send through SMTP server configured in Graphite, by default it's 'localhost'

Patches

Problem was patched in Graphite-web 1.1.6. Also patches was released for graphite-web 1.0.x and 0.9.x, and we'll discuss releases of non-supported branches later.

Workarounds

You can manually remove function send_email from file webapp/graphite/composer/views.py. This function are not in use and will not affect your Graphite installation.

References

For more information check this graphite-web Github issue #2008

For more information

If you have any questions or comments about this advisory:

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2017-18638 has been found in graphite-web.
Attackers can target a specific entry point like send_email over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade graphite-web to 1.1.6 or later.
If unsure, ask your IT team or search "graphite-web CVE-2017-18638" on the vendor's site.

CVE-2017-18638 (graphite-web) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: send_email
Patched: 1.1.6 — apply immediately
Workaround: You can manually remove function send_email from file webapp/graphite/composer/views.py.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in graphite-web. Attackers reach the vulnerable code path via send_email without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of graphite-web. Attack surface: send_email.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.1.6.

🛡️ Workaround

Workaround: You can manually remove function send_email from file webapp/graphite/composer/views.py.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'graphite-web' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'graphite-web' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で graphite-web を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    You can manually remove function `send_email` from file `webapp/graphite/composer/views.py`.

    パッチが適用されるまでの応急処置として、You can manually remove function send_email from file webapp/graphite/composer/views.py. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade graphite-web to 1.1.6

    ステージング環境で 1.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI graphite-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details