# CVE-2002-2139: Auth bypass in n/a

> Local users can hijack VPN sessions via man-in-the-middle attacks due to failure to delete duplicate ISAKMP SAs in Cisco PIX Firewalls.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Nov 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wvrc-375c-f654

## What is CVE-2002-2139?

CVE-2002-2139 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Nov 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cisco PIX Firewall 6.0.3 and earlier, and 6.1.x to 6.1.3, do not delete the duplicate ISAKMP SAs for a user's VPN session, which allows local users to hijack a session via a man-in-the-middle attack.

## Which versions are affected by CVE-2002-2139?

It affects 1 product.


Products: Cisco Pix Firewall Software.

## How do I fix CVE-2002-2139?

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

## Is CVE-2002-2139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1022](https://insights.sbomify.com/CVE-2000-1022/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-2140](https://insights.sbomify.com/CVE-2002-2140/): Memory corruption in n/a (medium 5.0)
- [CVE-2000-1027](https://insights.sbomify.com/CVE-2000-1027/): Information disclosure in n/a (medium 5.0)
- [CVE-1999-0158](https://insights.sbomify.com/CVE-1999-0158/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2139 and fix it if it is affected.

What it is: CVE-2002-2139 is a medium-severity authentication bypass vulnerability in n/a, published on 16 Nov 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-2139 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-2002-2139/ (Markdown: https://insights.sbomify.com/CVE-2002-2139/index.md)
```

## Sources

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

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