CVE-2010-2794 json
The SPICE (aka spice-xpi) plug-in 2.2 for Firefox allows local users to overwrite arbitrary files via a symlink attack on an unspecified lo…
published 16y ago modified 4mo ago also EUVD-2010-2798
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
The SPICE (aka spice-xpi) plug-in 2.2 for Firefox allows local users to overwrite arbitrary files via a symlink attack on an unspecified log file.
Patch / fix
- spice-xpi RHEL 5 PRODUCTIVITY, RHEL 5 2.2-2.3.el5_5
red hat advisories RHSA-2010:0651
Is CVE-2010-2794 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 FencerVendor 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-2794 updated cvss 2.1
spice-xpi symlink attack
-
Red Hat Enterprise Linux Desktop (v. 5 client) spice-xpi 2.2-2.3.el5_5 Red Hat Enterprise Linux Optional Productivity Applications (v. 5 server) spice-xpi 2.2-2.3.el5_5fixed: vendor fix RHSA-2010:0651
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.31% chance of exploitation in the next 30 days, higher than 24% 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:N/I:P/A:P |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
redhat.com
/support/errata/RHSA-2010-0651.html
vendor-advisory
- bugzilla.redhat.com /show_bug.cgi?id=620356
-
secunia.com
/advisories/41120
third-party-advisory
-
vupen.com
/english/advisories/2010/2181
vdb-entry
-
osvdb.org
/67620
vdb-entry
Sources
- CVE List CVE-2010-2794
- NVD CVE-2010-2794
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.