← Back
UBUNTU-CVE-2020-5208
Vulnerability in ipmitool (UBUNTU-CVE-2020-5208)
Summary
vulnerability in ipmitool (UBUNTU-CVE-2020-5208). Confidential information can be exposed externally. Mitigation: upgrade to `1.8.16-3ubuntu0.2+esm1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2020-5208** has been found in ipmitool.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade ipmitool to **1.8.16-3ubuntu0.2+esm1** or later.
If unsure, ask your IT team or search "ipmitool UBUNTU-CVE-2020-5208" on the vendor's site.
UBUNTU-CVE-2020-5208 (ipmitool) —
Attack vector: remote (network-reachable)
Patched: `1.8.16-3ubuntu0.2+esm1` — 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 ipmitool.
📍 Affected scope
ipmitool — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.8.16-3ubuntu0.2+esm1**.
🛡️ 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 'ipmitool' .` 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
-
1Identify exposure identify
grep -r 'ipmitool' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ipmitool` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ipmitool to 1.8.16-3ubuntu0.2+esm1ステージング環境で 1.8.16-3ubuntu0.2+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.16-3ubuntu0.2+esm1"}]}]
Ubuntu:18.04:LTS
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.18-5ubuntu0.2"}]}]
Ubuntu:20.04:LTS
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.18-8ubuntu0.1"}]}]
Ubuntu:24.04:LTS
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
ipmitool
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-5997-1
- report https://ubuntu.com/security/CVE-2020-5208
- report https://github.com/ipmitool/ipmitool/commit/e824c23316ae50beb7f7488f2055ac65e8b341f2
- report https://github.com/ipmitool/ipmitool/security/advisories/GHSA-g659-9qxw-p7cp
- report https://www.cve.org/CVERecord?id=CVE-2020-5208