| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in aMSN 0.90 and classified as problematic. Affected is an unknown function of the file hotlog.htm. This manipulation causes information disclosure. This vulnerability is handled as CVE-2004-2454. Additionally, an exploit exists. It is recommended to strengthen authentication.
Details
A vulnerability has been found in aMSN 0.90 and classified as problematic. Affected by this vulnerability is an unknown part of the file hotlog.htm. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
aMSN 0.90 for Microsoft Windows allows local users to obtain sensitive information such as hashed passwords from (1) hotlog.htm and (2) config.xml.
The bug was discovered 06/18/2004. The weakness was released 06/20/2004 by Lostmon Lords (Website). The advisory is shared at osvdb.org. This vulnerability is known as CVE-2004-2454 since 08/20/2005. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:hotlog.htm it is possible to find vulnerable targets with Google Hacking.
It is possible to mitigate the problem by adding an authentication mechanism.
The vulnerability is also documented in the databases at X-Force (16479), OSVDB (8123†) and SecurityTracker (ID 1010555†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍
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
06/18/2004 🔍06/20/2004 🔍
06/20/2004 🔍
06/21/2004 🔍
07/21/2004 🔍
12/31/2004 🔍
08/20/2005 🔍
03/09/2015 🔍
06/29/2018 🔍
Sources
Advisory: osvdb.org⛔Researcher: Lostmon Lords
Status: Not defined
Confirmation: 🔍
CVE: CVE-2004-2454 (🔍)
GCVE (CVE): GCVE-0-2004-2454
GCVE (VulDB): GCVE-100-23341
X-Force: 16479 - aMSN hotlog.htm allows attacker to obtain passwords
OSVDB: 8123 - aMSN hotlog.htm Password Disclosure
SecurityTracker: 1010555
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/09/2015 16:55Updated: 06/29/2018 10:28
Changes: 03/09/2015 16:55 (60), 06/29/2018 10:28 (1)
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.