SSRF (Server-Side Request Forgery) in glance (CVE-2017-7200)
Summary
SSRF in glance (CVE-2017-7200). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.0.0a0 or later.
Original description
The description as published by the source.
An SSRF issue was discovered in OpenStack Glance before Newton. The 'copy_from' feature in the Image Service API v1 allowed an attacker to perform masked network port scans. With v1, it is possible to create images with a URL such as 'http://localhost:22'. This could then allow an attacker to enumerate internal network details while appearing masked, since the scan would appear to originate from the Glance Image service.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-7200 has been found in glance.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade glance to 11.0.0a0 or later.
If unsure, ask your IT team or search "glance CVE-2017-7200" on the vendor's site.
CVE-2017-7200 (glance) — CWE-918 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 11.0.0a0 — apply immediately
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.
SSRF (CWE-918) exists in glance.
Check the vendor advisory for the affected versions of glance.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 11.0.0a0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'glance' . 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
-
1Identify exposure identify
grep -r 'glance' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
glanceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade glance to 11.0.0a0ステージング環境で 11.0.0a0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2017-7200 glance Fixed in: 2:13.0.0-1
References
- advisory securityfocus.com
- advisory bugs.launchpad.net
- advisory bugs.launchpad.net
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch wiki.openstack.org
- web github.com