Vulnerability in ironic-inspector (CVE-2019-10141)

Summary

vulnerability in ironic-inspector (CVE-2019-10141). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `7.2.4, 8.2.1, 5.0.2, 6.0.3, 8.0.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2019-10141** has been found in ironic-inspector. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade ironic-inspector to **7.2.4, 8.2.1, 5.0.2, 6.0.3, 8.0.3** or later. If unsure, ask your IT team or search "ironic-inspector CVE-2019-10141" on the vendor's site.

CVE-2019-10141 (ironic-inspector) — Patched: `7.2.4, 8.2.1, 5.0.2, 6.0.3, 8.0.3` — 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 ironic-inspector.

📍 Affected scope

ironic-inspector — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **7.2.4, 8.2.1, 5.0.2, 6.0.3, 8.0.3**.

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

Affected packages

PyPI ironic-inspector

[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.0"},{"fixed":"7.2.4"},{"introduced":"8.1.0"},{"fixed":"8.2.1"},{"introduced":"0"},{"fixed":"5.0.2"},{"introduced":"5.1.0"},{"fixed":"6.0.3"},{"introduced":"8.0.0"},{"fixed":"8.0.3"}]}]