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

> Aborting a passphrase prompt in nCipher ConsoleCallBack leaks the passphrase, potentially allowing attackers to gain privileges.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jx7j-h9w4-xcmv

## What is CVE-2002-0941?

CVE-2002-0941 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The ConsoleCallBack class for nCipher running under JRE 1.4.0 and 1.4.0_01, as used by the TrustedCodeTool and possibly other applications, may leak a passphrase when the user aborts an application that is prompting for the passphrase, which could allow attackers to gain privileges.

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

It affects 2 products.


Products: Ncipher Nforce, Ncipher Nshield.

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

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

## Is CVE-2002-0941 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0941 is a medium-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0941 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-0941/ (Markdown: https://insights.sbomify.com/CVE-2002-0941/index.md)
```

## Sources

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

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