# CVE-2009-2411: Integer overflow in n/a > Remote authenticated users or servers can execute arbitrary code via crafted svndiff streams due to integer overflows in the libsvn_delta library. - **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Aug 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-2411, DSA-1855-1, GHSA-vmfg-4frj-fmfg, RHSA-2009:1203 ## What is CVE-2009-2411? CVE-2009-2411 is a high-severity vulnerability in n/a, published on 7 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-189 ## Which versions are affected by CVE-2009-2411? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mod_dav_svn` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.4-3.el4_8.2 | | `subversion` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-perl` | Red Hat:enterprise_linux:4::as | All versions | 0:1.1.4-3.el4_8.2 | | `mod_dav_svn` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.4-3.el4_8.2 | | `subversion` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-perl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.1.4-3.el4_8.2 | | `mod_dav_svn` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.4-3.el4_8.2 | | `subversion` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-perl` | Red Hat:enterprise_linux:4::es | All versions | 0:1.1.4-3.el4_8.2 | | `mod_dav_svn` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.4-3.el4_8.2 | | `subversion` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.4-3.el4_8.2 | | `subversion-perl` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.1.4-3.el4_8.2 | | `mod_dav_svn` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-javahl` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-perl` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-ruby` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.4.2-4.el5_3.1 | | `mod_dav_svn` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-javahl` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-perl` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | | `subversion-ruby` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.2-4.el5_3.1 | Products: Subversion Subversion. ## How do I fix CVE-2009-2411? Upgrade to a fixed version. ## Is CVE-2009-2411 being exploited? There is no known exploitation of CVE-2009-2411 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2004-0397](https://insights.sbomify.com/CVE-2004-0397/): Memory corruption in n/a (high 7.5) - [CVE-2007-3846](https://insights.sbomify.com/CVE-2007-3846/): Path traversal in n/a (medium 6.0) - [CVE-2007-2448](https://insights.sbomify.com/CVE-2007-2448/): Information disclosure in n/a (low 2.1) - [CVE-2004-1438](https://insights.sbomify.com/CVE-2004-1438/): Missing authorization in n/a (low 2.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-2411 and fix it if it is affected. What it is: CVE-2009-2411 is a high-severity vulnerability in n/a, published on 7 Aug 2009. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2009-2411 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2009-2411/ (Markdown: https://insights.sbomify.com/CVE-2009-2411/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-2411 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-2411 - OSV: https://osv.dev/vulnerability/CVE-2009-2411 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-2411/ Summaries are generated and may contain mistakes; the official description above is the record.