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

> Attackers can read decrypted email content saved to disk when specific Outlook PGP plugin settings are enabled during replies.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cvr6-jvr3-rqhf

## What is CVE-2002-1696?

CVE-2002-1696 is a medium-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Microsoft Outlook plug-in PGP version 7.0, 7.0.3, and 7.0.4 silently saves a decrypted copy of a message to hard disk when "Automatically decrypt/verify when opening messages" option is checked, "Always use Secure Viewer when decrypting" option is not checked, and the user replies to an encrypted message.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Pgp Personal Privacy.

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

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

## Is CVE-2002-1696 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2069](https://insights.sbomify.com/CVE-2002-2069/): Information disclosure in n/a (high 7.5)
- [CVE-2000-0802](https://insights.sbomify.com/CVE-2000-0802/): Security feature bypass in n/a (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1696 is a medium-severity vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1696 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-1696/ (Markdown: https://insights.sbomify.com/CVE-2002-1696/index.md)
```

## Sources

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

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