# CVE-2002-0939: Security feature bypass in n/a

> The Install Wizard fails to enforce Operator Card Set protection, allowing keys to be stored with lower security than requested by the user.

- **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:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f262-3xjr-j8x9

## What is CVE-2002-0939?

CVE-2002-0939 is a medium-severity vulnerability in n/a, published on 31 Aug 2002. 

### Official description

The Install Wizard for nCipher MSCAPI CSP 5.50 does not use Operator Card Set protected keys when the user requests them but does not generate the Operator Card Set, which results in a lower protection level than specified by the user (module protection only).

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

It affects 1 product.


Products: Ncipher Mscapi Csp.

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

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

## Is CVE-2002-0939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0940](https://insights.sbomify.com/CVE-2002-0940/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0939 is a medium-severity vulnerability in n/a, published on 31 Aug 2002. 
Exploitation: There is no known exploitation of CVE-2002-0939 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-0939/ (Markdown: https://insights.sbomify.com/CVE-2002-0939/index.md)
```

## Sources

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

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