CVE-2004-0063
First published: Tue Feb 17 2004(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| nCipher PayShield | =1.3.12 | |
| nCipher PayShield | =1.5.18 | |
| nCipher PayShield | =1.6.18 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2004-0063?
CVE-2004-0063 is classified as a critical vulnerability due to its potential impact on security decisions in applications.
How do I fix CVE-2004-0063?
To fix CVE-2004-0063, update the nCipher payShield SPP library to a version later than 1.6.18.
What applications are affected by CVE-2004-0063?
Applications using the nCipher payShield SPP library versions 1.3.12, 1.5.18, and 1.6.18 are affected by CVE-2004-0063.
What are the risks associated with CVE-2004-0063?
The risks include allowing invalid PIN numbers to be accepted, thereby compromising security.
What does CVE-2004-0063 exploit?
CVE-2004-0063 exploits a flaw in the SPP_VerifyPVV function that improperly handles status codes from the hardware security module.
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/ncipher
- canonical/ncipher payshield
- version/ncipher payshield/1.3.12
- version/ncipher payshield/1.5.18
- version/ncipher payshield/1.6.18