# CVE-2013-1202: Denial of service in Cisco ACE

> Attackers can cause a denial of service on Cisco ACE load balancers by exploiting log retention mechanisms.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-6q3h-862r-76g5

## What is CVE-2013-1202?

CVE-2013-1202 is a high-severity denial of service vulnerability in Cisco ACE, published on 7 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco ACE A2(3.6) allows log retention DoS.

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

It affects 1 product.


Products: Cisco Ace Application Control Engine Module A2.

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

No fix has been published for CVE-2013-1202 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-1202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1202 is a high-severity denial of service vulnerability in Cisco ACE, published on 7 Feb 2020. 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-1202 in the wild and no public exploit code.

Affected product: Cisco ACE. 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-1202/ (Markdown: https://insights.sbomify.com/CVE-2013-1202/index.md)
```

## Sources

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

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