Vulnerability in libvirt (UBUNTU-CVE-2024-1441)

Summary

Vulnerability in libvirt (UBUNTU-CVE-2024-1441). Risk of unauthorized operations or information disclosure. Exploitable via names. Mitigation: upgrade to 1.2.2-0ubuntu13.1.28+esm2 or later.

Original description

The description as published by the source.

An off-by-one error flaw was found in the udevListInterfacesByStatus() function in libvirt when the number of interfaces exceeds the size of the names array. This issue can be reproduced by sending specially crafted data to the libvirt daemon, allowing an unprivileged client to perform a denial of service attack by causing the libvirt daemon to crash.

Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2024-1441 has been found in libvirt.
Attackers can target a specific entry point like names over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libvirt to 1.2.2-0ubuntu13.1.28+esm2 or later.
If unsure, ask your IT team or search "libvirt UBUNTU-CVE-2024-1441" on the vendor's site.

UBUNTU-CVE-2024-1441 (libvirt)
Attack vector: local / no user interaction
Attack surface: names
Patched: 1.2.2-0ubuntu13.1.28+esm2 — 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 libvirt. Attackers reach the vulnerable code path via names.

📍 Affected scope

Check the vendor advisory for the affected versions of libvirt. Attack surface: names.

🔥 Severity

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

🔧 How to fix

Update to 1.2.2-0ubuntu13.1.28+esm2.

🛡️ 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 'libvirt' . 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
Identify exposure identify
```
grep -r 'libvirt' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libvirt を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade libvirt to 1.2.2-0ubuntu13.1.28+esm2
```
ステージング環境で 1.2.2-0ubuntu13.1.28+esm2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.2-0ubuntu13.1.28+esm2"}]}]

Ubuntu:Pro:16.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.1-1ubuntu10.31+esm1"}]}]

Ubuntu:Pro:18.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-1ubuntu8.21+esm1"}]}]

Ubuntu:20.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.0-0ubuntu8.19"}]}]

Ubuntu:22.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.0-1ubuntu7.10"}]}]

Ubuntu:24.04:LTS libvirt

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.0.0-2ubuntu8.1"}]}]

References

advisory ubuntu.com
advisory ubuntu.com
advisory ubuntu.com
report ubuntu.com
report access.redhat.com
report cve.org