TowerBlog 0.2/0.4 R1/0.6/0.6 R1 Login dat/login Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TowerBlog 0.2/0.4 R1/0.6/0.6 R1. It has been classified as critical. Affected is an unknown function of the file dat/login of the component Login. The manipulation leads to Remote Code Execution. This vulnerability is referenced as CVE-2005-1055. Furthermore, an exploit is available. It is recommended to add further authentication.
Details
A vulnerability was found in TowerBlog 0.2/0.4 R1/0.6/0.6 R1. It has been rated as critical. This issue affects an unknown code block of the file dat/login of the component Login. The manipulation with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
TowerBlog 0.6 and earlier stores the login data file under the web root, which allows remote attackers to obtain the MD5 checksums of the username and password via a direct request to the _dat/login file.
The bug was discovered 04/11/2005. The weakness was published 04/10/2005 by Corry L. (Website). It is possible to read the advisory at securitytracker.com. The identification of this vulnerability is CVE-2005-1055 since 04/12/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a exploit are known.
After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 18015 , which helps to determine the existence of the flaw in a target environment.
It is possible to mitigate the problem by adding an authentication mechanism.
The vulnerability is also documented in the databases at X-Force (20039), Tenable (18015), SecurityFocus (BID 13090†), OSVDB (15425†) and Secunia (SA14884†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 18015
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: AuthenticationStatus: 🔍
0-Day Time: 🔍
Timeline
04/10/2005 🔍04/10/2005 🔍
04/10/2005 🔍
04/11/2005 🔍
04/11/2005 🔍
04/11/2005 🔍
04/11/2005 🔍
04/11/2005 🔍
04/11/2005 🔍
04/12/2005 🔍
04/18/2005 🔍
03/10/2015 🔍
07/01/2021 🔍
Sources
Advisory: securitytracker.com⛔Researcher: Corry L.
Status: Confirmed
CVE: CVE-2005-1055 (🔍)
GCVE (CVE): GCVE-0-2005-1055
GCVE (VulDB): GCVE-100-24155
X-Force: 20039
SecurityFocus: 13090
Secunia: 14884 - TowerBlog Exposure of Sensitive Information, Less Critical
OSVDB: 15425 - TowerBlog _dat/login Admin Credential Disclosure
SecurityTracker: 1013675
Vulnerability Center: 7626 - TowerBlog 0.6 Disclosure of User Credentials, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/10/2015 23:05Updated: 07/01/2021 15:00
Changes: 03/10/2015 23:05 (68), 05/31/2019 14:59 (1), 07/01/2021 15:00 (4)
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.