nCipher Payshield SPP Library 1.3.12 SPP_VerifyPVV privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in nCipher Payshield SPP Library 1.3.12. It has been rated as problematic. Affected is the function SPP_VerifyPVV. The manipulation leads to privileges management.
This vulnerability is documented as CVE-2004-0063. There is not any exploit available.
Details
A vulnerability was found in nCipher Payshield SPP Library 1.3.12 (Software Library). It has been rated as critical. This issue affects the function SPP_VerifyPVV. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was released 12/12/2003 (Website). The advisory is shared at ncipher.com. The identification of this vulnerability is CVE-2004-0063. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (14832), SecurityFocus (BID 9422†), OSVDB (3537†) and Secunia (SA10648†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/12/2003 🔍01/14/2004 🔍
01/16/2004 🔍
01/16/2004 🔍
02/17/2004 🔍
10/15/2014 🔍
07/05/2017 🔍
Sources
Advisory: ncipher.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2004-0063 (🔍)
GCVE (CVE): GCVE-0-2004-0063
GCVE (VulDB): GCVE-100-21581
X-Force: 14832 - Payshield incorrect request verification
SecurityFocus: 9422 - nCipher payShield SPP Library Bad Request Verification Vulnerability
Secunia: 10648 - nCipher payShield May Authorize Transactions With Wrong PIN, Less Critical
OSVDB: 3537 - nCipher payShield SPP Library Bad Request Verification
Entry
Created: 10/15/2014 14:25Updated: 07/05/2017 09:02
Changes: 10/15/2014 14:25 (53), 07/05/2017 09:02 (8)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.