Skip to content
Fencer Vulns
medium 4.6

CVE-2005-2693 json

cvsbug in CVS 1.12.12 and earlier creates temporary files insecurely, which allows local users to overwrite arbitrary files and execute arb…

published 2005-08-25 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2694

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

Summary

cvsbug in CVS 1.12.12 and earlier creates temporary files insecurely, which allows local users to overwrite arbitrary files and execute arbitrary code via a symlink attack.

Patch / fix

  • cvs Debian 14, Debian 13, Debian 12 1:1.11.5-4

debian advisories DEBIAN-CVE-2005-2693

  • cvs RHEL 3 1.11.2-28
  • cvs RHEL 4 1.11.17-8.RHEL4

red hat advisories RHSA-2005:756

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-2005-2693 updated

security flaw

  • Red Hat Desktop version 3 cvs 1.11.2-28 Red Hat Enterprise Linux AS version 3 cvs 1.11.2-28 Red Hat Enterprise Linux AS version 4 cvs 1.11.17-8.RHEL4 Red Hat Enterprise Linux Desktop version 4 cvs 1.11.17-8.RHEL4 Red Hat Enterprise Linux ES version 3 cvs 1.11.2-28 Red Hat Enterprise Linux ES version 4 cvs 1.11.17-8.RHEL4
    +2 more products
    Red Hat Enterprise Linux WS version 3 cvs 1.11.2-28 Red Hat Enterprise Linux WS version 4 cvs 1.11.17-8.RHEL4
    fixed: vendor fix RHSA-2005:756

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

CVSS scores

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

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.