SubversionApplication · Apache
CVE-2015-0202
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe mod_dav_svn server in Subversion 1.8.0 through 1.8.11 allows remote attackers to cause a denial of service (memory consumption) via a large number of REPORT requests, which trigger the traversal of FSFS repository nodes.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencemod_dav_svn server in Subversion 1.8.0-1.8.11 allows remote attackers to cause denial of service via memory consumption by sending a large number of REPORT requests, which trigger excessive FSFS repository node traversal.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SubversionApplication
= 1.8.0= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7= 1.8.8= 1.8.9= 1.8.10= 1.8.11= 13.1= 13.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Subversion versionRun `svn --version` or check package manager: `rpm -q subversion` (RHEL/CentOS) or `dpkg -l subversion` (Debian/Ubuntu)Affected if Version is 1.8.0 through 1.8.11 inclusive
-
Verify mod_dav_svn module is loadedRun `httpd -M 2>/dev/null | grep dav_svn` or `apache2ctl -M 2>/dev/null | grep dav_svn` to list loaded Apache modules, or inspect Apache config files for `LoadModule dav_svn_module`Affected if mod_dav_svn is loaded and active in Apache configuration
-
Confirm WebDAV REPORT requests are enabledInspect Apache configuration for Subversion repositories (commonly in `/etc/httpd/conf.d/subversion.conf`, `/etc/apache2/mods-enabled/dav_svn.conf`, or similar) and verify the `DAV svn` directive is presentAffected if Server is configured to serve Subversion repositories via WebDAV (DAV svn) allowing REPORT requests
-
Identify repository storage backend typeCheck repository format: look for `format` file in repository root (e.g., `<repo_path>/format`) or run `svnadmin info <repo-path>` and look for `Repository Format` or `FSFS` in the outputAffected if Repository uses FSFS backend (default for SVN 1.8), which is required for this attack to trigger node traversal
If Subversion version is 1.8.0-1.8.11 AND mod_dav_svn is loaded serving FSFS repositories via WebDAV, the server is vulnerable to memory exhaustion via crafted REPORT requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Subversion to version 1.8.12 or later to patch this vulnerability; alternatively, implement rate limiting on REPORT requests at the network or web server level as a temporary mitigation.
Fix this in Subversion
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-0202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data