Vulnerability in glance (CVE-2012-4573)

Summary

vulnerability in glance (CVE-2012-4573). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2012-4573** has been found in glance. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade glance to **90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc** or later. If unsure, ask your IT team or search "glance CVE-2012-4573" on the vendor's site.

CVE-2012-4573 (glance) — Patched: `90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc` — 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

**A vulnerability** (unclassified) exists in glance.

📍 Affected scope

glance — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc**.

🛡️ 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 (7 steps)

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

1
Identify exposure identify
```
grep -r 'glance' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `glance` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade glance to 90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc
```
ステージング環境で 90bcdc5a89e350a358cf320a03f5afe99795f6f6, efd7e75b1f419a52c7103c7840e24af8e5deb29d, 6ab0992e5472ae3f9bef0d2ced41030655d9d2bc に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI glance

[{"repo":"https:\/\/github.com\/openstack\/glance","type":"GIT","events":[{"introduced":"0"},{"fixed":"90bcdc5a89e350a358cf320a03f5afe99795f6f6"},{"fixed":"efd7e75b1f419a52c7103c7840e24af8e5deb29d"},{"fixed":"6ab0992e5472ae3f9bef0d2ced41030655d9d2bc"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]