# CVE-2002-1108: Security feature bypass in n/a

> Attackers can bypass tunnel security in Cisco VPN Client by forcing acknowledgment of external TCP packets when all tunnel mode is enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mvq9-7wg5-rmxc

## What is CVE-2002-1108?

CVE-2002-1108 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Virtual Private Network (VPN) Client software 2.x.x, and 3.x before 3.6(Rel), when configured with all tunnel mode, can be forced into acknowledging a TCP packet from outside the tunnel.

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

It affects 1 product.


Products: Cisco Vpn Client.

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

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

## Is CVE-2002-1108 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1106](https://insights.sbomify.com/CVE-2002-1106/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-1107](https://insights.sbomify.com/CVE-2002-1107/): Weak cryptography in n/a (high 7.5)
- [CVE-2015-7600](https://insights.sbomify.com/CVE-2015-7600/): Privilege escalation in n/a (high 7.2)
- [CVE-2006-2679](https://insights.sbomify.com/CVE-2006-2679/): Privilege escalation in n/a (high 7.2)
- [CVE-2002-1447](https://insights.sbomify.com/CVE-2002-1447/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1108 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. 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-2002-1108 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-1108/ (Markdown: https://insights.sbomify.com/CVE-2002-1108/index.md)
```

## Sources

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

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