Skip to content
Fencer Intel
low 3.3

CVE-2010-2792 json

Race condition in the SPICE (aka spice-xpi) plug-in 2.2 for Firefox allows local users to obtain sensitive information, and conduct man-in-…

published 16y ago modified 4mo ago also EUVD-2010-2796

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

Race condition in the SPICE (aka spice-xpi) plug-in 2.2 for Firefox allows local users to obtain sensitive information, and conduct man-in-the-middle attacks, by providing a UNIX socket for communication between this plug-in and the client (aka qspice-client) in qspice 0.3.0, and then accessing this socket.

Patch / fix

  • spice-xpi RHEL 5 PRODUCTIVITY, RHEL 5 2.2-2.3.el5_5
  • qspice-client RHEL 5 PRODUCTIVITY, RHEL 5 0.3.0-4.el5_5

red hat advisories RHSA-2010:0651RHSA-2010:0632

Is CVE-2010-2792 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-2792 updated cvss 3.3

spice-xpi/qspice-client unix socket race

  • Red Hat Enterprise Linux Desktop (v. 5 client) spice-xpi 2.2-2.3.el5_5, qspice-client 0.3.0-4.el5_5 Red Hat Enterprise Linux Optional Productivity Applications (v. 5 server) spice-xpi 2.2-2.3.el5_5, qspice-client 0.3.0-4.el5_5
    fixed: vendor fix RHSA-2010:0632

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:P/I:P/A:N

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.