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

> Remote attackers can steal cleartext passwords via sniffing when Cisco VPN concentrators use RADIUS with PAP or Challenge authentication.

- **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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8cqc-9wjh-xjr2

## What is CVE-2002-0848?

CVE-2002-0848 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco VPN 5000 series concentrator hardware 6.0.21.0002 and earlier, and 5.2.23.0003 and earlier, when using RADIUS with a challenge type of Password Authentication Protocol (PAP) or Challenge, sends the user password in cleartext in a validation retry request, which could allow remote attackers to steal passwords via sniffing.

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

It affects 1 product.


Products: Cisco Vpn 5000 Concentrator Series Software.

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

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

## Is CVE-2002-0848 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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