LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25651: A flaw was found in the SPICE file transfer protocol.

A flaw was found in the SPICE file transfer protocol. File data from the host system can end up in full or in parts in the client connection of an illegitimate local user in the VM system. Active file transfers from other users could also be interrupted, resulting in a denial of service. The highest threat from this vulnerability is to data confidentiality as well as system availability. This flaw affects spice-vdagent versions 0.20 and prior.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-25651 is a flaw in the SPICE file transfer protocol used by spice-vdagent. In affected VM environments, host file-transfer data could be exposed to an unauthorized local user inside the VM, and active transfers could be disrupted. The main business concern is unintended data exposure during VM file transfers.

Executive priority

Treat this as a moderate-priority virtualization hygiene issue. It is not evidenced as internet-scale or actively exploited in the provided sources, but it can expose host file-transfer data in affected VM workflows and should be remediated through normal patch management.

Technical view

The issue is identified as CWE-362, indicating a race-condition class flaw. It affects spice-vdagent versions 0.20 and prior. The CVE description states host file data may appear fully or partially in an illegitimate local user's VM client connection, and other users' transfers may be interrupted, causing denial of service.

Likely exposure

Exposure is most likely where spice-vdagent 0.20 or earlier is installed and SPICE file transfer is enabled in VM or virtual desktop workflows. Multi-user guest systems and shared environments have higher practical risk. Environments without spice-vdagent or SPICE file transfer are less likely to be affected.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described attacker position is local and inside the VM system, which limits reach but matters in shared desktop, lab, hosting, or administrative VM environments.

Researcher notes

Key evidence is the CVE description, CWE-362 classification, and distribution advisories from Debian and Fedora. Public scoring details are absent in the supplied bundle, and fixed package versions are not listed here. Avoid assuming exploit availability or broader product impact beyond spice-vdagent.

Mitigation direction

  • Inventory systems running spice-vdagent 0.20 or earlier.
  • Apply distribution security updates for spice-vdagent when available.
  • Review Debian, Fedora, and vendor advisories for fixed package guidance.
  • Disable SPICE file transfer where it is not operationally required.
  • Reduce shared local-user access on affected VM guests.

Validation and detection

  • Check installed spice-vdagent package versions against 0.20 and prior.
  • Confirm vendor security updates are applied on affected distributions.
  • Review VM configurations for enabled SPICE file transfer.
  • Identify multi-user guests where unauthorized local access is plausible.
  • Monitor user reports of interrupted or misdirected file transfers.
Prepared
Confidence
medium
Sources
7

Public sources used

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-362: 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-2020-25651 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
6Source links

CVSS and timeline data

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aspice-vdagentspice-vdagent versions 0.20 and priorListed
Weakness

CWE details

CWE-362

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

CWE-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs