LiveActive security incident?Get immediate response
CVE Record

CVE-2021-3592: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU.

An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_input() function and could occur while processing a udp packet that is smaller than the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytes of uninitialized heap memory from the host. The highest threat from this vulnerability is to data confidentiality. This flaw affects libslirp versions prior to 4.6.0.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-3592 is a QEMU SLiRP networking flaw that can let a malicious virtual machine guest leak a small amount of uninitialized heap memory from the host. The reported leak is 10 bytes, so the direct impact is confidentiality, not system takeover. Exposure depends on using vulnerable libslirp before 4.6.0.

Executive priority

Treat this as a moderate-priority confidentiality issue for environments running untrusted virtual machines. It is not described as actively exploited, but it crosses a guest-to-host data boundary, so patching should be included in normal virtualization security maintenance.

Technical view

The issue is an invalid pointer initialization in SLiRP bootp_input() while processing a UDP packet smaller than bootp_t. A guest can trigger disclosure of 10 bytes of uninitialized host heap memory. The CVE identifies CWE-824 and affects libslirp versions prior to 4.6.0, including QEMU deployments using that vulnerable SLiRP code.

Likely exposure

Most relevant exposure is virtualization hosts, CI runners, lab hypervisors, or appliances running QEMU with SLiRP/user-mode networking and libslirp before 4.6.0 or an unpatched vendor package.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The attacker position is a malicious guest able to send crafted network traffic through vulnerable SLiRP processing. Evidence supports limited host memory disclosure, not guest escape or code execution.

Researcher notes

The key boundary is guest-to-host disclosure via SLiRP BOOTP handling. The source bundle states a 10-byte uninitialized heap leak and libslirp prior to 4.6.0. No CVSS vector, public exploit status, or broader impact is provided in the supplied evidence.

Mitigation direction

  • Inventory QEMU hosts and appliances using SLiRP or libslirp.
  • Update libslirp to 4.6.0 or a vendor-patched package.
  • Apply relevant Fedora, Gentoo, Debian, NetApp, or platform vendor advisories.
  • Reduce use of untrusted guests on vulnerable user-mode networking paths.
  • Check vendor guidance before applying nonstandard workarounds.

Validation and detection

  • Confirm installed libslirp package version or vendor backport status.
  • Identify QEMU configurations using SLiRP/user-mode networking.
  • Review virtualization platforms for untrusted guest workloads.
  • Verify security updates from the relevant distribution or vendor are installed.
  • Document systems where QEMU embeds or statically links libslirp.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-824: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-3592 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aQEMUlibslirp 4.6.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-824 · source CWE mapping

Access of Uninitialized Pointer

Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.