Vulnerability in sushy-tools (CVE-2022-44020)
Summary
Vulnerability in sushy-tools (CVE-2022-44020). Data can be tampered with by attackers. Mitigation: upgrade to 0.21.1 or later.
Original description
The description as published by the source.
An issue was discovered in OpenStack Sushy-Tools through 0.21.0 and VirtualBMC through 2.2.2. Changing the boot device configuration with these packages removes password protection from the managed libvirt XML domain. NOTE: this only affects an "unsupported, production-like configuration."
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2022-44020 has been found in sushy-tools.
Data can be tampered with by attackers.
What to do: upgrade sushy-tools to 0.21.1 or later.
If unsure, ask your IT team or search "sushy-tools CVE-2022-44020" on the vendor's site.
CVE-2022-44020 (sushy-tools) — CWE-281
Attack vector: local / no user interaction
Patched: 0.21.1 — 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.
A vulnerability (CWE-281) exists in sushy-tools.
Check the vendor advisory for the affected versions of sushy-tools.
Severity: ?. Data can be tampered with by attackers.
Update to 0.21.1.
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 'sushy-tools' . 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 'sushy-tools' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sushy-toolsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sushy-tools to 0.21.1ステージング環境で 0.21.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web review.opendev.org
- web review.opendev.org
- web storyboard.openstack.org