| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in moziloWiki up to 1.0.1 and classified as problematic. Affected is an unknown function of the file print.php. Executing a manipulation of the argument page can lead to path traversal. This vulnerability is registered as CVE-2008-6129. No exploit is available.
Details
A vulnerability classified as problematic was found in moziloWiki up to 1.0.1 (Content Management System). This vulnerability affects an unknown code of the file print.php. The manipulation of the argument page 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. CVE summarizes:
Directory traversal vulnerability in print.php in moziloWiki 1.0.1 and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the page parameter.
The weakness was published 02/13/2009 by David Vieira-Kurz (Website). The advisory is shared for download at wiki.mozilo.de. This vulnerability was named CVE-2008-6129 since 02/13/2009. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.
It is declared as highly functional. By approaching the search of inurl:print.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (45523), SecurityFocus (BID 31493†) and Secunia (SA32024†). Similar entries are available at VDB-46542 and VDB-46541. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 🔍
Status: Highly functional
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
09/30/2008 🔍09/30/2008 🔍
02/13/2009 🔍
02/13/2009 🔍
02/13/2009 🔍
03/17/2015 🔍
10/28/2018 🔍
Sources
Advisory: wiki.mozilo.deResearcher: David Vieira-Kurz
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-6129 (🔍)
GCVE (CVE): GCVE-0-2008-6129
GCVE (VulDB): GCVE-100-46540
X-Force: 45523 - moziloWiki print.php directory traversal
SecurityFocus: 31493 - moziloWiki Prior to 1.0.2 Multiple Vulnerabilities
Secunia: 32024 - moziloWiki Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/17/2015 16:11Updated: 10/28/2018 07:58
Changes: 03/17/2015 16:11 (54), 10/28/2018 07:58 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.