CVE-2020-25653: Race Condition

Published Oct 8, 2020
·
Updated

A race condition vulnerability was found in the way the spice-vdagentd daemon handled new client connections. This flaw may allow an unprivileged local guest user to become the active agent for spice-vdagentd, possibly resulting in a denial of service or information leakage from the host. 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.

Other sources

The following flaw was reported by SUSE Security:

One major security property of spice-vdagentd is that it only allows those clients access to most of the SPICE features (like clipboard, file transfer) that are currently in an active session according to systemd. It is possible for arbitrary local users (like nobody) to connect to spice-vdagentd but these connections should not be able to interact with the host machine, because they don't belong to the active session.

There is a race condition between the point in time when a client performs the connect() call to establish a connection with spice-vdagentd and the time spice-vdagentd retrieves and checks the PID in its agentconnect() function. The described race condition is very hard to hit under normal circumstances, because the agentconnect() function in spice-vdagentd is very likely to run before an unrelated process gets reassigned the malicious PID in question. When combined with the file descriptor exhaustion security issue however, then this attack will become way more feasible.

An unprivileged local attacker inside a VM could use this flaw to become the "active agent" for spice-vdagentd for the graphical session of a legitimate local user. If successful then the attacker can access the host's clipboard contents or send malicious clipboard content to the host. The attacker can also retrieve file data from the host or send invalid screen resolution and display information to the host. If the victim's graphical session already runs a legitimate spice-vdagent then a successful attack will trigger an information leak protection logic in vdagentd.c:874. This has the effect of a denial-of-service, because neither the attacker nor the legitimate user will be able to use the SPICE features anymore.

Red Hat

Affected Software

5 affected componentsFixes available
redhat/spice-vdagent<0.21.0
0.21.0
Spice-space Spice-vdagent<=0.20.0
Debian Debian Linux=9.0
Fedoraproject Fedora=32
Fedoraproject Fedora=33

Event History

Nov 26, 2020
CVE Published
via MITRE·01:23 AM
Data Sourced
via MITRE·01:23 AM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-25653?

CVE-2020-25653 is a race condition vulnerability found in the spice-vdagentd daemon, which handles new client connections.

2

What is the impact of CVE-2020-25653?

CVE-2020-25653 may allow an unprivileged local guest user to become the active agent for spice-vdagentd, resulting in a denial of service or information leakage from the host.

3

What software versions are affected by CVE-2020-25653?

Versions up to and including 0.20.0 of spice-vdagent, Debian Linux 9.0, Fedora 32, and Fedora 33 are affected.

4

How severe is CVE-2020-25653?

CVE-2020-25653 has a severity rating of 6.3 (medium).

5

How do I fix CVE-2020-25653?

To fix CVE-2020-25653, update to version 0.21.0 of spice-vdagent.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203