Skip to content
Fencer Intel
medium 6.8

CVE-2010-4539 json

The walk function in repos.c in the mod_dav_svn module for the Apache HTTP Server, as distributed in Apache Subversion before 1.6.15, allow…

published 2011-01-07 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4505

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

Summary

The walk function in repos.c in the mod_dav_svn module for the Apache HTTP Server, as distributed in Apache Subversion before 1.6.15, allows remote authenticated users to cause a denial of service (NULL pointer dereference and daemon crash) via vectors that trigger the walking of SVNParentPath collections.

Patch / fix

  • subversion Debian 14, Debian 13, Debian 12 1.6.12dfsg-4

debian advisories DEBIAN-CVE-2010-4539

  • subversion RHEL 6 1.6.11-2.el6_0.2
  • mod_dav_svn RHEL 6 1.6.11-2.el6_0.2
  • subversion-kde RHEL 6 1.6.11-2.el6_0.2
  • subversion-perl RHEL 6 1.6.11-2.el6_0.2
  • subversion-ruby RHEL 6 1.6.11-2.el6_0.2
  • subversion-gnome RHEL 6 1.6.11-2.el6_0.2
  • subversion-javahl RHEL 6 1.6.11-2.el6_0.2
  • subversion-svn2cl RHEL 6 1.6.11-2.el6_0.2

red hat advisories RHSA-2011:0258RHSA-2011:0257

  • subversion openSUSE Tumbleweed 1.9.5-1.1

opensuse advisories openSUSE-SU-2024:10538-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-2010-4539 updated cvss 3.5

(mod_dav_svn): DoS (crash) by processing certain requests to display all available repositories to a web browser

  • Red Hat Enterprise Linux (v. 5.6.z server) subversion 1.6.11-7.el5_6.1, mod_dav_svn 1.6.11-7.el5_6.1, subversion-perl 1.6.11-7.el5_6.1, subversion-ruby 1.6.11-7.el5_6.1, subversion-javahl 1.6.11-7.el5_6.1
    fixed: vendor fix RHSA-2011:0257
  • Red Hat Enterprise Linux Desktop Optional (v. 6) subversion 1.6.11-2.el6_0.2, mod_dav_svn 1.6.11-2.el6_0.2, subversion-kde 1.6.11-2.el6_0.2, subversion-perl 1.6.11-2.el6_0.2, subversion-ruby 1.6.11-2.el6_0.2, subversion-gnome 1.6.11-2.el6_0.2, +2 more Red Hat Enterprise Linux HPC Node Optional (v. 6) subversion 1.6.11-2.el6_0.2, mod_dav_svn 1.6.11-2.el6_0.2, subversion-kde 1.6.11-2.el6_0.2, subversion-perl 1.6.11-2.el6_0.2, subversion-ruby 1.6.11-2.el6_0.2, subversion-gnome 1.6.11-2.el6_0.2, +2 more Red Hat Enterprise Linux Server (v. 6) subversion 1.6.11-2.el6_0.2, mod_dav_svn 1.6.11-2.el6_0.2, subversion-javahl 1.6.11-2.el6_0.2 Red Hat Enterprise Linux Server Optional (v. 6) subversion 1.6.11-2.el6_0.2, subversion-kde 1.6.11-2.el6_0.2, subversion-perl 1.6.11-2.el6_0.2, subversion-ruby 1.6.11-2.el6_0.2, subversion-gnome 1.6.11-2.el6_0.2, subversion-javahl 1.6.11-2.el6_0.2, +1 more Red Hat Enterprise Linux Workstation (v. 6) subversion 1.6.11-2.el6_0.2, mod_dav_svn 1.6.11-2.el6_0.2, subversion-javahl 1.6.11-2.el6_0.2 Red Hat Enterprise Linux Workstation Optional (v. 6) subversion 1.6.11-2.el6_0.2, subversion-kde 1.6.11-2.el6_0.2, subversion-perl 1.6.11-2.el6_0.2, subversion-ruby 1.6.11-2.el6_0.2, subversion-gnome 1.6.11-2.el6_0.2, subversion-svn2cl 1.6.11-2.el6_0.2
    fixed: vendor fix RHSA-2011:0258
  • Red Hat Enterprise Linux 4 subversion
    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

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

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=667407 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-399 Resource Management Errors

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.