LiveActive security incident?Get immediate response
CVE Record

CVE-2021-3595: 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 tftp_input() function and could occur while processing a udp packet that is smaller than the size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or indirect host memory disclosure to the guest. 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

This issue can let a virtual machine guest read unintended host memory through QEMU's SLiRP networking code. The cited sources describe a confidentiality impact, not system takeover. Risk is highest where QEMU uses vulnerable libslirp versions before 4.6.0, especially in environments with untrusted or shared guest workloads.

Executive priority

Treat this as a moderate-priority virtualization confidentiality issue. It is not documented here as actively exploited, but it crosses the guest-to-host trust boundary. Prioritize patching shared virtualization hosts, developer sandboxes, CI runners, and any environment running untrusted guest workloads.

Technical view

CVE-2021-3595 is a CWE-824 invalid pointer initialization flaw in libslirp's TFTP handling, specifically tftp_input(). A UDP packet smaller than the expected tftp_t structure can cause out-of-bounds read behavior or indirect disclosure of host memory to the guest. The bundle states libslirp versions before 4.6.0 are affected.

Likely exposure

Exposure is most likely in QEMU deployments using SLiRP/libslirp user-mode networking with vulnerable libslirp packages before 4.6.0. Distribution advisories from Fedora, Gentoo, and Debian indicate operating-system package impact and updates. NetApp also published an advisory, so appliance or embedded QEMU dependencies should be checked with vendor guidance.

Exploitation context

The provided bundle does not report active exploitation, and KEV is false. The described attack context is guest-to-host confidentiality exposure through malformed network input processed by SLiRP TFTP code. No public exploit status, exploitation prevalence, or authentication details are established in the supplied sources.

Researcher notes

Key uncertainty is severity: the bundle provides no CVSS vector. The most important technical boundary is vulnerable libslirp before 4.6.0 in QEMU SLiRP networking. Validate package backports carefully, because distro package versions may not match upstream 4.6.0 while still containing the security fix.

Mitigation direction

  • Update libslirp to 4.6.0 or later where vendor packages support it.
  • Apply QEMU security updates from the relevant OS or appliance vendor.
  • Review Fedora, Gentoo, Debian, and NetApp advisories for product-specific guidance.
  • Reduce use of SLiRP networking for untrusted guests where operationally feasible.
  • Track vendor advisories if embedded QEMU dependencies are not directly visible.

Validation and detection

  • Inventory hosts running QEMU and record installed libslirp package versions.
  • Flag libslirp versions earlier than 4.6.0 for remediation review.
  • Confirm relevant OS advisories are applied through package manager records.
  • Identify VM configurations using SLiRP or user-mode networking.
  • Check appliance vendor bulletins for bundled QEMU or libslirp exposure.
Prepared
Confidence
medium
Sources
9

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-3595 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
8Source 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.