Skip to content
Fencer Vulns
medium 6.0

CVE-2007-3919 json

(1) xenbaked and (2) xenmon.py in Xen 3.1 and earlier allow local users to truncate arbitrary files via a symlink attack on /tmp/xenq-shm.

published 2007-10-28 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-3903

cvss
6.0
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 26%
public exploits
0
none known

Summary

(1) xenbaked and (2) xenmon.py in Xen 3.1 and earlier allow local users to truncate arbitrary files via a symlink attack on /tmp/xenq-shm.

Patch / fix

  • xen RHEL 5 VIRTUALIZATION, RHEL 5 3.0.3-41.el5_1.5
  • xen-libs RHEL 5 3.0.3-41.el5_1.5

red hat advisories RHSA-2008:0194

  • xen openSUSE Tumbleweed 4.15.1_01-1.2

opensuse advisories openSUSE-SU-2024:11520-1

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-2007-3919 updated

xen xenmon.py / xenbaked insecure temporary file accesss

  • Red Hat Enterprise Linux (v. 5 server) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Desktop (v. 5 client) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Desktop Multi OS (v. 5 client) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Virtualization (v. 5 server) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5
    fixed: vendor fix RHSA-2008:0194

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.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Vulns 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.