Skip to content
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2020-25637 →
Unrated

Vulnerability in libvirt

UBUNTU-CVE-2020-25637 First seen on SecPulse

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-2020-25637 has been found in libvirt.
Successful exploitation can lead to full system takeover.
What to do: upgrade libvirt to 4.0.0-1ubuntu8.21 or later.
If unsure, ask your IT team or search "libvirt UBUNTU-CVE-2020-25637" on the vendor's site.

UBUNTU-CVE-2020-25637 (libvirt)
Attack vector: local / no user interaction
Patched: 4.0.0-1ubuntu8.21 — 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.

Affected scope

Check the vendor advisory for the affected versions of libvirt.

Severity

Severity: ?. Successful exploitation can lead to full system takeover.

How to fix

Update to 4.0.0-1ubuntu8.21.

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. 1
    Identify exposureidentify
    grep -r 'libvirt' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libvirt を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade libvirt to 4.0.0-1ubuntu8.21

    ステージング環境で 4.0.0-1ubuntu8.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Ubuntu:Pro:14.04:LTS libvirt
All versions
—
Ubuntu:Pro:16.04:LTS libvirt
All versions
—
Ubuntu:18.04:LTS libvirt
< 4.0.0-1ubuntu8.21
4.0.0-1ubuntu8.21
Ubuntu:20.04:LTS libvirt
< 6.0.0-0ubuntu8.16
6.0.0-0ubuntu8.16
Original description The description as published by the source.

A double free memory issue was found to occur in the libvirt API, in versions before 6.8.0, responsible for requesting information about network interfaces of a running QEMU domain. This flaw affects the polkit access control driver. Specifically, clients connecting to the read-write socket with limited ACL permissions could use this flaw to crash the libvirt daemon, resulting in a denial of service, or potentially escalate their privileges on the system. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details