# CVE-2011-2549: Denial of service in n/a

> Remote attackers can cause a denial of service on Cisco ASR 9000 routers by sending a malicious IPv4 packet, triggering a line-card reload.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hw43-vchf-c8qg

## What is CVE-2011-2549?

CVE-2011-2549 is a high-severity denial of service vulnerability in Cisco Ios Xr, published on 28 Jul 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Cisco IOS XR 4.1.x before 4.1.1 on Cisco Aggregation Services Routers (ASR) 9000 series devices allows remote attackers to cause a denial of service (line-card reload) via an IPv4 packet, aka Bug ID CSCtr26695.

## Which versions are affected by CVE-2011-2549?

It affects 3 products.


Products: Cisco Asr 9006 Router, Cisco Asr 9010 Router, Cisco Ios Xr.

## How do I fix CVE-2011-2549?

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

## Is CVE-2011-2549 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2549 and fix it if it is affected.

What it is: CVE-2011-2549 is a high-severity denial of service vulnerability in Cisco Ios Xr, published on 28 Jul 2011. 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-2011-2549 in the wild and no public exploit code.

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

## Sources

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

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