# CVE-2008-0537: Denial of service in n/a

> Remote attackers can cause denial of service on Cisco devices using MPLS VPN and OSPF sham-link configurations.

- **Severity:** High 7.1 (`AV:N/AC:M/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:** 27 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3x27-pvp2-3h6m

## What is CVE-2008-0537?

CVE-2008-0537 is a high-severity denial of service vulnerability in n/a, published on 27 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Supervisor Engine 32 (Sup32), Supervisor Engine 720 (Sup720), and Route Switch Processor 720 (RSP720) for multiple Cisco products, when using Multi Protocol Label Switching (MPLS) VPN and OSPF sham-link, allows remote attackers to cause a denial of service (blocked queue, device restart, or memory leak) via unknown vectors.

## Which versions are affected by CVE-2008-0537?

It affects 2 products.


Products: Cisco Route Switch Processor, Cisco Supervisor Engine.

## How do I fix CVE-2008-0537?

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

## Is CVE-2008-0537 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0537 and fix it if it is affected.

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

## Sources

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

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