# CVE-2013-5552: Security feature bypass in n/a

> Remote attackers can bypass access restrictions on Cisco IOS CSG devices by exploiting a flaw in the parse error drop feature.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x583-rp6c-xwgv

## What is CVE-2013-5552?

CVE-2013-5552 is a medium-severity vulnerability in Cisco Ios, published on 13 Nov 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco IOS 12.4(24)MDB9 and earlier on Content Services Gateway (CSG) devices does not properly implement the "parse error drop" feature, which allows remote attackers to bypass intended access restrictions via a crafted series of packets, aka Bug ID CSCug90143.

Weakness: CWE-264

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

It affects 2 products.


Products: Cisco Content Services Gateway, Cisco Ios.

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

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

## Is CVE-2013-5552 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5552 is a medium-severity vulnerability in Cisco Ios, published on 13 Nov 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-5552 in the wild and no public exploit code.

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

## Sources

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

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