| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in 1Scripts CodeDB 1.1.1. This impacts an unknown function of the file list.php. This manipulation of the argument lang causes path traversal. This vulnerability is handled as CVE-2008-3190. Additionally, an exploit exists.
Details
A vulnerability was found in 1Scripts CodeDB 1.1.1. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file list.php. The manipulation of the argument lang with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Directory traversal vulnerability in list.php in 1Scripts CodeDB 1.1.1 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the lang parameter.
The weakness was released 07/16/2008 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2008-3190 since 07/16/2008. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:list.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (43761), Exploit-DB (6071), SecurityFocus (BID 30227†) and Secunia (SA31053†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
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: Path traversalCWE: CWE-22
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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/14/2008 🔍07/15/2008 🔍
07/16/2008 🔍
07/16/2008 🔍
07/16/2008 🔍
03/17/2015 🔍
11/01/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Confirmed
CVE: CVE-2008-3190 (🔍)
GCVE (CVE): GCVE-0-2008-3190
GCVE (VulDB): GCVE-100-43261
X-Force: 43761 - CodeDB list.php file include
SecurityFocus: 30227 - CodeDB 'list.php' Local File Include Vulnerability
Secunia: 31053 - CodeDB "lang" Local File Inclusion Vulnerability, Moderately Critical
Vupen: ADV-2008-2105
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 12:19Updated: 11/01/2024 23:53
Changes: 03/17/2015 12:19 (53), 09/29/2018 12:59 (10), 11/01/2024 23:53 (22)
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.