| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in TCPDB 3.8. This affects an unknown part of the file user/index.php. Executing a manipulation can lead to improper authentication. This vulnerability is handled as CVE-2009-1670. Additionally, an exploit exists.
Details
A vulnerability has been found in TCPDB 3.8 and classified as critical. This vulnerability affects an unknown part of the file user/index.php. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
user/index.php in TCPDB 3.8 does not require administrative authentication, which allows remote attackers to add admin accounts via unspecified vectors. NOTE: some of these details are obtained from third party information.
The weakness was released 05/07/2009 (Website). The advisory is available at milw0rm.com. This vulnerability was named CVE-2009-1670 since 05/18/2009. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:user/index.php 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 (50371), SecurityFocus (BID 34866†), OSVDB (54282†) and Secunia (SA34966†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 900551
OpenVAS Name: TCPDB Security Bypass Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
05/07/2009 🔍05/07/2009 🔍
05/07/2009 🔍
05/08/2009 🔍
05/18/2009 🔍
05/18/2009 🔍
03/17/2015 🔍
11/29/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2009-1670 (🔍)
GCVE (CVE): GCVE-0-2009-1670
GCVE (VulDB): GCVE-100-48226
X-Force: 50371
SecurityFocus: 34866 - TCPDB 'user/index.php' Authentication Bypass Vulnerability
Secunia: 34966
OSVDB: 54282 - TCPDB user/index.php Direct Request Admin Authentication Bypass
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 23:38Updated: 11/29/2024 02:16
Changes: 03/17/2015 23:38 (55), 08/14/2017 10:25 (5), 08/11/2021 09:52 (3), 11/29/2024 02:16 (20)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.