Skip to content
Fencer Intel
low 3.3

CVE-2013-4277 json

Svnserve in Apache Subversion 1.4.0 through 1.7.12 and 1.8.0 through 1.8.1 allows local users to overwrite arbitrary files or kill arbitrar…

published 13y ago modified 4mo ago also EUVD-2013-4176

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

Summary

Svnserve in Apache Subversion 1.4.0 through 1.7.12 and 1.8.0 through 1.8.1 allows local users to overwrite arbitrary files or kill arbitrary processes via a symlink attack on the file specified by the --pid-file option.

Patch / fix

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

debian advisories DEBIAN-CVE-2013-4277

  • subversion openSUSE Tumbleweed 1.9.5-1.1

opensuse advisories openSUSE-SU-2024:10538-1

Is CVE-2013-4277 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-4277 updated cvss 3.6

subversion: svnserve is 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
    affected: no fix planned “Will not fix”
  • 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.69% chance of exploitation in the next 30 days, higher than 52% 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-264 Permissions, Privileges, and Access Controls

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.