Skip to content
Fencer Intel
low 2.4

CVE-2013-7393 json

The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created…

published 12y ago modified 4mo ago also EUVD-2013-7159

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

Summary

The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created for (1) svnwcsub.py or (2) irkerbridge.py when the --pidfile option is used. NOTE: this issue was SPLIT from CVE-2013-4262 based on different affected versions (ADT3).

Patch / fix

  • subversion Debian 14, Debian 13, Debian 12 1.8.5-1

debian advisories DEBIAN-CVE-2013-7393

Is CVE-2013-7393 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-2013-7393 updated cvss 2.6

subversion: svnwcsub.py and irkerbridge.py are vulnerable to symlink attack

  • Red Hat Enterprise Linux 5 subversion Red Hat Enterprise Linux 6 subversion, mod_dav_svn, subversion-kde, subversion-perl, subversion-ruby, subversion-gnome, +2 more Red Hat Enterprise Linux 7 subversion, mod_dav_svn, subversion-kde, subversion-libs, subversion-perl, subversion-ruby, +4 more
    not affected: vulnerable code not present

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

CVSS scores

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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.