SubversionApplication · Apache
CVE-2013-1847
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 Apache HTTPD server module in Subversion 1.6.0 through 1.6.20 and 1.7.0 through 1.7.8 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an anonymous LOCK for a URL that does not exist.
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 confidenceThe mod_dav_svn Apache HTTPD server module in Subversion versions 1.6.0-1.6.20 and 1.7.0-1.7.8 contains a NULL pointer dereference vulnerability when handling anonymous LOCK requests for URLs that do not exist, leading to a denial of service (server crash).
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.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4= 1.6.5= 1.6.6= 1.6.7= 1.6.8= 1.6.9= 1.6.10= 1.6.11CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 if mod_dav_svn is loaded in ApacheCheck your Apache configuration for the 'mod_dav_svn' module load directive, or run 'httpd -M' or 'apachectl -M' to list loaded modules and look for 'dav_svn_module'.Affected if mod_dav_svn is loaded and serving Subversion repositories through Apache.
-
Check the installed Subversion server versionRun 'svnadmin --version' or 'svn --version' on the server to get the Subversion version number, or check the installed package version via your system's package manager.Affected if The version is 1.6.0 through 1.6.20, or 1.7.0 through 1.7.8.
-
Verify if anonymous access to repositories is permittedReview your Apache configuration for the SVNPath or SVNParentPath directives and check if they allow unauthenticated access (no 'Require valid-user' or similar restrictions on the relevant Location blocks).Affected if Anonymous or unauthenticated users can access the Subversion repositories via Apache.
-
Confirm WebDAV LOCK method is enabledCheck the Apache configuration for the mod_dav module being loaded (usually 'LoadModule dav_module modules/mod_dav.so') and verify the DAV directive is set to 'DAV svn' within the Subversion Location block.Affected if The DAV svn directive is present, enabling WebDAV LOCK operations on repositories.
Your environment is affected if you are running a Subversion server version 1.6.0-1.6.20 or 1.7.0-1.7.8 with mod_dav_svn loaded in Apache, and anonymous users can send LOCK requests to non-existent URLs within accessible repositories.
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 server to version 1.6.21, 1.7.9, or later (including 1.8.x) to patch the NULL pointer dereference in mod_dav_svn's LOCK request handling for non-existent URLs.
Fix this in Subversion
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1847 — 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-2013-1847 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