CRYPTOCard CRYPTOAdmin 4.1 on PalmOS PIN improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CRYPTOCard CRYPTOAdmin 4.1 on PalmOS. It has been rated as problematic. This affects an unknown part of the component PIN Handler. Performing a manipulation results in improper authentication. This vulnerability is known as CVE-2000-0275. Furthermore, an exploit is available.
Details
A vulnerability classified as problematic has been found in CRYPTOCard CRYPTOAdmin 4.1 on PalmOS. This affects an unknown function of the component PIN Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality. The summary by CVE is:
CRYPTOCard CryptoAdmin for PalmOS uses weak encryption to store a user s PIN number, which allows an attacker with access to the .PDB file to generate valid PT-1 tokens after cracking the PIN.
The weakness was published 04/10/2000 with @stake (Website). It is possible to read the advisory at l0pht.com. This vulnerability is uniquely identified as CVE-2000-0275. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept.
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 Exploit-DB (19838) and SecurityFocus (BID 1097†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.7
VulDB Base Score: 4.0
VulDB Temp Score: 3.7
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/10/2000 🔍04/10/2000 🔍
04/10/2000 🔍
06/24/2014 🔍
11/22/2024 🔍
Sources
Advisory: l0pht.comResearcher: Discovered by Kingpin
Organization: @stake
Status: Not defined
CVE: CVE-2000-0275 (🔍)
GCVE (CVE): GCVE-0-2000-0275
GCVE (VulDB): GCVE-100-15435
SecurityFocus: 1097 - CRYPTOCard CRYPTOAdmin 4.1 Weak Encryption Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/24/2014 11:02Updated: 11/22/2024 04:52
Changes: 06/24/2014 11:02 (49), 05/23/2018 11:08 (6), 10/08/2020 17:54 (1), 11/22/2024 04:52 (21)
Complete: 🔍
Cache ID: 216:CF2:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.