# CVE-2013-1896: Denial of service in n/a > Remote attackers can cause a denial of service via a crafted MERGE request when mod_dav_svn is configured, affecting Apache HTTP Server. - **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jul 2013 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2013-1896, GHSA-g852-xcg2-2w9v, MGASA-2013-0230, RHSA-2013:1156 ## What is CVE-2013-1896? CVE-2013-1896 is a medium-severity denial of service vulnerability in Apache Http Server, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description mod_dav.c in the Apache HTTP Server before 2.2.25 does not properly determine whether DAV is enabled for a URI, which allows remote attackers to cause a denial of service (segmentation fault) via a MERGE request in which the URI is configured for handling by the mod_dav_svn module, but a certain href attribute in XML data refers to a non-DAV URI. ## Which versions are affected by CVE-2013-1896? It affects 9 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `httpd` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.3-82.el5_9 | | `httpd-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.3-82.el5_9 | | `httpd-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.3-82.el5_9 | | `httpd-manual` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.3-82.el5_9 | | `mod_ssl` | Red Hat:enterprise_linux:5::server | All versions | 1:2.2.3-82.el5_9 | | `httpd` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.15-29.el6_4 | | `httpd-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.15-29.el6_4 | | `httpd-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.15-29.el6_4 | | `httpd-manual` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.15-29.el6_4 | | `httpd-tools` | Red Hat:enterprise_linux:6::client | All versions | 0:2.2.15-29.el6_4 | | `mod_ssl` | Red Hat:enterprise_linux:6::client | All versions | 1:2.2.15-29.el6_4 | | `httpd` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.15-29.el6_4 | | `httpd-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.15-29.el6_4 | | `httpd-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.15-29.el6_4 | | `httpd-manual` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.15-29.el6_4 | | `httpd-tools` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.2.15-29.el6_4 | | `mod_ssl` | Red Hat:enterprise_linux:6::computenode | All versions | 1:2.2.15-29.el6_4 | | `httpd` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.15-29.el6_4 | | `httpd-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.15-29.el6_4 | | `httpd-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.15-29.el6_4 | | `httpd-manual` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.15-29.el6_4 | | `httpd-tools` | Red Hat:enterprise_linux:6::server | All versions | 0:2.2.15-29.el6_4 | | `mod_ssl` | Red Hat:enterprise_linux:6::server | All versions | 1:2.2.15-29.el6_4 | | `httpd` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.15-29.el6_4 | | `httpd-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.15-29.el6_4 | | `httpd-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.15-29.el6_4 | | `httpd-manual` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.15-29.el6_4 | | `httpd-tools` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.2.15-29.el6_4 | | `mod_ssl` | Red Hat:enterprise_linux:6::workstation | All versions | 1:2.2.15-29.el6_4 | Products: Apache Http Server, Canonical Ubuntu Linux, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Workstation, Redhat Jboss Enterprise Application Platform. ## How do I fix CVE-2013-1896? Upgrade to a fixed version. ## Is CVE-2013-1896 being exploited? There is no known exploitation of CVE-2013-1896 in the wild and no public exploit code. ## Other vulnerabilities in Apache Http Server - [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild) - [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild) - [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild) - [CVE-2019-0211](https://insights.sbomify.com/CVE-2019-0211/): Apache HTTP Server Privilege Escalation (high 7.8, exploited in the wild) - [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-1896 and fix it if it is affected. What it is: CVE-2013-1896 is a medium-severity denial of service vulnerability in Apache Http Server, published on 10 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-1896 in the wild and no public exploit code. Affected product: Apache Http Server. 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-2013-1896/ (Markdown: https://insights.sbomify.com/CVE-2013-1896/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-1896 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-1896 - OSV: https://osv.dev/vulnerability/CVE-2013-1896 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-1896/ Summaries are generated and may contain mistakes; the official description above is the record.