| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Text Rider 2.4. This impacts an unknown function of the file data/userlist.txt. The manipulation results in information disclosure. This vulnerability was named CVE-2006-0439. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Text Rider 2.4. Affected is an unknown code block of the file data/userlist.txt. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
Text Rider 2.4 stores sensitive data in the data directory under the web document root with insufficient access control, which allows remote attackers to obtain usernames and password hashes by directly accessing data/userlist.txt.
The weakness was presented 01/26/2006 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2006-0439 since 01/26/2006. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
It is declared as proof-of-concept. By approaching the search of inurl:data/userlist.txt it is possible to find vulnerable targets with Google Hacking.
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 (24279), Secunia (SA18605†) and SecurityTracker (ID 1015533†). See VDB-28489 for similar entry. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/24/2006 🔍01/25/2006 🔍
01/26/2006 🔍
01/26/2006 🔍
01/26/2006 🔍
03/12/2015 🔍
07/31/2017 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2006-0439 (🔍)
GCVE (CVE): GCVE-0-2006-0439
GCVE (VulDB): GCVE-100-28488
X-Force: 24279 - Text Rider data directory information disclosure
Secunia: 18605 - Text Rider Exposure of User Credentials, Highly Critical
SecurityTracker: 1015533 - Text Rider Lets Remote Users Obtain Authentication Information
Vupen: ADV-2006-0321
See also: 🔍
Entry
Created: 03/12/2015 11:11Updated: 07/31/2017 08:57
Changes: 03/12/2015 11:11 (52), 07/31/2017 08:57 (6)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.