# CVE-2002-1492: Memory corruption in n/a

> Local attackers can exploit buffer overflows in the Cisco VPN Client to gain root privileges on Linux and Solaris systems.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v4vf-x3rr-p95c

## What is CVE-2002-1492?

CVE-2002-1492 is a high-severity memory corruption vulnerability in n/a, published on 18 Mar 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflows in the Cisco VPN 5000 Client before 5.2.7 for Linux, and VPN 5000 Client before 5.2.8 for Solaris, allow local users to gain root privileges via (1) close_tunnel and (2) open_tunnel.

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

It affects 1 product.


Products: Cisco Vpn 5000 Client.

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

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

## Is CVE-2002-1492 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1492 exists.

Public exploit code:

- Cisco VPN 5000 Client - Buffer Overrun (1) (exploitdb)
- Cisco VPN 5000 Client - Buffer Overrun (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1491](https://insights.sbomify.com/CVE-2002-1491/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1492 is a high-severity memory corruption vulnerability in n/a, published on 18 Mar 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1492 exists.

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-1492/ (Markdown: https://insights.sbomify.com/CVE-2002-1492/index.md)
```

## Sources

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

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