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

> Remote attackers can identify PGPfire usage via modified ICMP packets, revealing the presence of the security software.

- **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:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8h4q-w278-x888

## What is CVE-2002-0208?

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

### Official description

PGP Security PGPfire 7.1 for Windows alters the system's TCP/IP stack and modifies packets in ICMP error messages in a way that allows remote attackers to determine that the system is running PGPfire.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Network.associates Pgpfire.

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

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

## Is CVE-2002-0208 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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