# CVE-2002-1099: Information disclosure in n/a

> Remote attackers can access sensitive information without authentication by directly accessing specific HTML pages on Cisco VPN Concentrators.

- **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-5x6v-v8hw-r85j

## What is CVE-2002-1099?

CVE-2002-1099 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 VPN 3000 Concentrator 2.2.x, and 3.x before 3.5.3, allows remote attackers to obtain potentially sensitive information without authentication by directly accessing certain HTML pages.

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

It affects 2 products.


Products: Cisco Vpn 3000 Concentrator Series Software, Cisco Vpn 3002 Hardware Client.

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

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

## Is CVE-2002-1099 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0483](https://insights.sbomify.com/CVE-2006-0483/): Denial of service in n/a (high 7.8)
- [CVE-2002-1092](https://insights.sbomify.com/CVE-2002-1092/): Auth bypass in n/a (high 7.5)
- [CVE-2002-1096](https://insights.sbomify.com/CVE-2002-1096/): Information disclosure in n/a (high 7.5)
- [CVE-2002-1097](https://insights.sbomify.com/CVE-2002-1097/): Information disclosure in n/a (high 7.5)
- [CVE-2002-1098](https://insights.sbomify.com/CVE-2002-1098/): Misconfiguration in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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