Skip to content
Fencer Intel
high 8.8

CVE-2013-4246 json

libsvn_fs_fs/fs_fs.c in Apache Subversion 1.8.x before 1.8.2 might allow remote authenticated users with commit access to corrupt FSFS repo…

published 9y ago modified 4mo ago also EUVD-2013-4150

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

libsvn_fs_fs/fs_fs.c in Apache Subversion 1.8.x before 1.8.2 might allow remote authenticated users with commit access to corrupt FSFS repositories and cause a denial of service or obtain sensitive information by editing packed revision properties.

Patch / fix

  • subversion openSUSE Tumbleweed 1.9.5-1.1

opensuse advisories openSUSE-SU-2024:10538-1

Is CVE-2013-4246 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-4246 updated cvss 5.5

subversion: FSFS repository corruption due to editing packed revision properties

  • 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

2.82% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness

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.