| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in spb kiosk engine 1.0.0.1 and classified as problematic. This affects an unknown part. The manipulation leads to information disclosure. This vulnerability is documented as CVE-2005-4589. There is not any exploit available. Adding more authentication is recommended.
Details
A vulnerability, which was classified as problematic, has been found in spb kiosk engine 1.0.0.1. This issue affects an unknown part. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
spb kiosk engine 1.0.0.1 stores the administrator s passcode in the registry in plaintext which allows local users to obtain the passcode.
The weakness was released 12/30/2005 by Seth Fogie (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2005-4589 since 12/30/2005. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After even before and not, there has been an exploit disclosed. The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
It is possible to mitigate the problem by adding an authentication mechanism.
The vulnerability is also documented in the databases at X-Force (23894), OSVDB (22033†), Secunia (SA18243†) and SecurityTracker (ID 1015413†). Entry connected to this vulnerability is available at VDB-27822. 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: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.0
VulDB Temp Score: 3.9
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: AuthenticationStatus: 🔍
0-Day Time: 🔍
Timeline
12/24/2005 🔍12/27/2005 🔍
12/28/2005 🔍
12/28/2005 🔍
12/30/2005 🔍
12/30/2005 🔍
12/30/2005 🔍
03/12/2015 🔍
08/03/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Seth Fogie
Status: Not defined
CVE: CVE-2005-4589 (🔍)
GCVE (CVE): GCVE-0-2005-4589
GCVE (VulDB): GCVE-100-27821
X-Force: 23894 - Spb Kiosk Engine plaintext passcode
Secunia: 18243 - Spb Kiosk Engine Program Execution Control Bypass Weakness, Not Critical
OSVDB: 22033 - Spb Kiosk Engine Registry Cleartext Administrator Credential Disclosure
SecurityTracker: 1015413 - Spb Kiosk Engine Discloses Administrative Password to Local Users
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 08/03/2017 03:15
Changes: 03/12/2015 11:11 (52), 08/03/2017 03:15 (11)
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.