| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Aladdin eToken 3.3.3. This issue affects some unknown processing of the component EEPROM. Performing a manipulation results in improper authentication. This vulnerability is known as CVE-2000-0427. Furthermore, an exploit is available. This vulnerability is historically significant due to its background and the way it was received. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Aladdin eToken 3.3.3. This affects some unknown processing of the component EEPROM. 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, integrity, and availability. The summary by CVE is:
The Aladdin Knowledge Systems eToken device allows attackers with physical access to the device to obtain sensitive information without knowing the PIN of the owner by resetting the PIN in the EEPROM.
The weakness was published 05/04/2000 (Website). The advisory is shared at l0pht.com. This vulnerability is uniquely identified as CVE-2000-0427. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/20/2025). Due to its background and reception, this vulnerability has a historic impact.
After immediately, there has been an exploit disclosed. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (4434), Exploit-DB (19894), SecurityFocus (BID 1170†) and OSVDB (3266†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.9
VulDB Temp Score: 5.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: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
05/04/2000 🔍05/04/2000 🔍
05/04/2000 🔍
05/04/2000 🔍
12/31/2003 🔍
06/24/2014 🔍
03/20/2025 🔍
Sources
Advisory: l0pht.comStatus: Confirmed
CVE: CVE-2000-0427 (🔍)
GCVE (CVE): GCVE-0-2000-0427
GCVE (VulDB): GCVE-100-15525
X-Force: 4434
SecurityFocus: 1170 - Aladdin Knowledge Systems eToken PIN Extraction Vulnerability
OSVDB: 3266 - eToken Private PIN Bypass
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/24/2014 15:42Updated: 03/20/2025 07:18
Changes: 06/24/2014 15:42 (57), 05/24/2018 21:31 (2), 03/20/2025 07:18 (19)
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.