dbcve.org
SubversionApplication · Apache

CVE-2013-2112

HIGH · 7.8 CVSS v2.0 Published 2013-07-31
Fix available
A fix is available. Upgrade to after 1.6.21 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The svnserve server in Subversion before 1.6.23 and 1.7.x before 1.7.10 allows remote attackers to cause a denial of service (exit) by aborting a connection.

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 confidence

The svnserve server in Subversion versions before 1.6.23 and 1.7.x before 1.7.10 contains a flaw where aborting a connection causes the server process to exit, allowing remote attackers to crash the service and cause denial of service.

MitigationUpgrade Subversion server to version 1.6.23 or later, or 1.7.10 or later, to patch the vulnerability and prevent premature process termination on connection abort.

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
Affected:<= 1.6.21= 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
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.04
SubversionApplication
Affected:= 1.6.17
OpensuseOperating system
Affected:= 11.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if svnserve is in use
    Run 'ps aux | grep svnserve' or check if port 3690 is listening (svnserve default port) using 'netstat -anp | grep 3690' or 'ss -tlnp | grep 3690'
    Affected if svnserve process is running or port 3690 is open and listening
  2. Determine installed Subversion version
    Run 'svnserve --version' or 'svn --version' to obtain the installed version number
    Affected if version output shows 1.7.x before 1.7.10, or 1.6.x at 1.6.21 or lower, or matches any of these specific versions: 1.6.0 through 1.6.21, 1.6.17 (Collabnet)
  3. Confirm Subversion package source
    Check package manager output: 'dpkg -l | grep subversion' on Debian/Ubuntu, 'rpm -qa | grep subversion' on RHEL-based systems, or 'zypper se subversion' on SUSE
    Affected if installed package version matches the affected ranges from step 2

If svnserve is active and the installed Subversion version is 1.7.x before 1.7.10 or 1.6.x at 1.6.21 or lower, the environment is vulnerable to remote denial of service via connection abort.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.6.21
Interim mitigation

Upgrade Subversion server to version 1.6.23 or later, or 1.7.10 or later, to patch the vulnerability and prevent premature process termination on connection abort.

Fix this in Subversion Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2112 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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