# CVE-2013-4558: Denial of service in n/a

> Remote attackers can cause a denial of service via a non-canonical URL in Subversion's mod_dav_svn module when assertions and SVNAutoversioning are enabled.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** 7 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4558, GHSA-6c6v-jhrm-ff4w

## What is CVE-2013-4558?

CVE-2013-4558 is a low-severity denial of service vulnerability in n/a, published on 7 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The get_parent_resource function in repos.c in mod_dav_svn Apache HTTPD server module in Subversion 1.7.11 through 1.7.13 and 1.8.1 through 1.8.4, when built with assertions enabled and SVNAutoversioning is enabled, allows remote attackers to cause a denial of service (assertion failure and Apache process abort) via a non-canonical URL in a request, as demonstrated using a trailing /.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-4558?

It affects 2 products.


Products: Apache Mod Dav Svn, Apache Subversion.

## How do I fix CVE-2013-4558?

Upgrade to a fixed version.

## Is CVE-2013-4558 being exploited?

There is no known exploitation of CVE-2013-4558 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4558 and fix it if it is affected.

What it is: CVE-2013-4558 is a low-severity denial of service vulnerability in n/a, published on 7 Dec 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-4558 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-2013-4558/ (Markdown: https://insights.sbomify.com/CVE-2013-4558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4558
- OSV: https://osv.dev/vulnerability/CVE-2013-4558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4558/
Summaries are generated and may contain mistakes; the official description above is the record.