dbcve.org
SubversionApplication

CVE-2009-2411

HIGH · 8.5 CVSS v2.0 Published 2009-08-07
Fix available
A fix is available. Upgrade to after 1.5.6 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Multiple integer overflows in the libsvn_delta library in Subversion before 1.5.7, and 1.6.x before 1.6.4, allow remote authenticated users and remote Subversion servers to execute arbitrary code via an svndiff stream with large windows that trigger a heap-based buffer overflow, a related issue to CVE-2009-2412.

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

Integer overflows in libsvn_delta's svndiff stream parsing allow specially crafted svndiff data with large windows to cause heap-based buffer overflows, enabling remote authenticated users or malicious Subversion servers to execute arbitrary code.

MitigationUpgrade Subversion to version 1.5.7 or later (1.5.x branch) or 1.6.4 or later (1.6.x branch) to patch the vulnerable libsvn_delta library.

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.5.6= 0.22.1= 0.23.0= 0.24.0= 0.24.1= 0.24.2= 0.25.0= 0.27.0= 0.28.0= 0.28.1= 0.28.2= 0.29.0

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
M
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:S/C:C/I:C/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. Check if Subversion is installed
    Run 'svn --version' or 'svnserve --version' to see if the Subversion client or server is present
    Affected if No Subversion installation found means not affected
  2. Determine installed Subversion version
    Run 'svn --version' (client) or 'svnadmin --version' (server tools) to get the exact version number
    Affected if Version output shows a vulnerable version (1.5.6 or lower, or any of these: 0.22.1, 0.23.0, 0.24.0-0.24.2, 0.25.0, 0.27.0, 0.28.0-0.28.2, 0.29.0)
  3. Locate the libsvn_delta library
    Run 'locate libsvn_delta' or check the Subversion library path (typically /usr/lib or /usr/local/lib) for libsvn_delta.so
    Affected if The library exists and belongs to a vulnerable Subversion version
  4. Verify the svndiff streaming feature is in use
    Check if the system processes Subversion repositories (check for active svnserve processes, HTTP access to Subversion repositories, or local repo access via file://)
    Affected if System processes svndiff data through vulnerable libsvn_delta code (applies to any Subversion client or server using the affected library)

You are affected if any installed Subversion version (client or server) matches 1.5.6 or lower, or any of the specific 0.xx versions listed, and that installation uses libsvn_delta to process svndiff streams.

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.5.6
Interim mitigation

Upgrade Subversion to version 1.5.7 or later (1.5.x branch) or 1.6.4 or later (1.6.x branch) to patch the vulnerable libsvn_delta library.

Fix this in Subversion Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-2411 — 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-2009-2411 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