# CVE-2000-0700: Security feature bypass in n/a

> Remote attackers can bypass ACLs or cause packet forwarding failures on Cisco GSR devices by exploiting improper handling of line card failures.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/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:** No
- **Published:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v7r2-f6jx-59j6

## What is CVE-2000-0700?

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

### Official description

Cisco Gigabit Switch Routers (GSR) with Fast Ethernet / Gigabit Ethernet cards, from IOS versions 11.2(15)GS1A up to 11.2(19)GS0.2 and some versions of 12.0, do not properly handle line card failures, which allows remote attackers to bypass ACLs or force the interface to stop forwarding packets.

## Which versions are affected by CVE-2000-0700?

It affects 4 products.


Products: Cisco Gigabit Switch Router 12008, Cisco Gigabit Switch Router 12012, Cisco Gigabit Switch Router 12016, Cisco Ios.

## How do I fix CVE-2000-0700?

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

## Is CVE-2000-0700 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0700 and fix it if it is affected.

What it is: CVE-2000-0700 is a medium-severity vulnerability in Cisco Ios, published on 13 Oct 2000. 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-2000-0700 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-2000-0700/ (Markdown: https://insights.sbomify.com/CVE-2000-0700/index.md)
```

## Sources

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

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