Skip to content
Medium 6.5

Information Disclosure in glance

CVE-2013-1840 First seen on SecPulse

Summary

Vulnerability in glance (CVE-2013-1840). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.0.0a0 or later.

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-2013-1840 has been found in glance.
Risk of unauthorized operations or information disclosure.
What to do: upgrade glance to 11.0.0a0 or later.
If unsure, ask your IT team or search "glance CVE-2013-1840" on the vendor's site.

CVE-2013-1840 (glance) — CWE-200
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.

What is the problem

Information disclosure (CWE-200) exists in glance.

Affected scope

Check the vendor advisory for the affected versions of glance.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to 11.0.0a0.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

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

  1. 1
    Identify exposureidentify
    grep -r 'glance' . | grep -v node_modules

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

  2. 2
    Apply patchpatch
    Upgrade glance to 11.0.0a0

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

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

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

Affected packages

PackageAffected → Fixed
PyPIglance
≤ v1→ Not listed
pipglance
< 11.0.0a0→ 11.0.0a0
Red HatOpenStack Folsom for RHEL 6 —
Red HatRed Hat OpenStack Platform 16.2 —
Red HatRed Hat OpenStack Platform 17.1 —
Red HatRed Hat OpenStack Platform 18.0 —

Fix status by distribution

Records published by each distribution for this CVE. Fixed versions differ by release; check each link.

Original description The description as published by the source.

The v1 API in OpenStack Glance Essex (2012.1), Folsom (2012.2), and Grizzly, when using the single-tenant Swift or S3 store, reports the location field, which allows remote authenticated users to obtain the operator's backend credentials via a request for a cached image.

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

References

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