Rivetcode RivetTracker 0.1/0.8 config.php cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Rivetcode RivetTracker 0.1/0.8. Affected by this issue is some unknown functionality of the file config.php. This manipulation causes cryptographic issue. This vulnerability appears as CVE-2008-7207. In addition, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Rivetcode RivetTracker 0.1/0.8 and classified as problematic. Affected by this vulnerability is an unknown code of the file config.php. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality. The summary by CVE is:
RivetTracker before 1.0 stores passwords in cleartext in config.php, which allows local users to discover passwords by reading config.php.
The weakness was presented 01/03/2008 (Website). It is possible to read the advisory at rivetcode.com. This vulnerability is known as CVE-2008-7207 since 09/11/2009. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
After before and not just, 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 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:config.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (42433†). 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.6
VulDB Base Score: 4.0
VulDB Temp Score: 3.6
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: Cryptographic issueCWE: CWE-310
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: RivetTracker 0.1
Timeline
01/03/2008 🔍01/03/2008 🔍
03/02/2008 🔍
09/11/2009 🔍
09/11/2009 🔍
03/18/2015 🔍
01/20/2019 🔍
Sources
Advisory: rivetcode.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2008-7207 (🔍)
GCVE (CVE): GCVE-0-2008-7207
GCVE (VulDB): GCVE-100-49963
OSVDB: 42433 - RivetTracker config.php Cleartext Admin Credential Local Disclosure
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/18/2015 15:15Updated: 01/20/2019 13:25
Changes: 03/18/2015 15:15 (53), 01/20/2019 13:25 (2)
Complete: 🔍
Cache ID: 216::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.