Gerrit Van Aaken Loudblog 0.41 index.php Language path traversal

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Gerrit Van Aaken Loudblog 0.41. The affected element is an unknown function of the file index.php. This manipulation of the argument Language causes path traversal. This vulnerability is handled as CVE-2006-1114. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Gerrit Van Aaken Loudblog 0.41 and classified as problematic. Affected by this vulnerability is some unknown functionality of the file index.php. The manipulation of the argument language 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, and integrity. The summary by CVE is:

Multiple directory traversal vulnerabilities in Loudblog before 0.42 allow remote attackers to read or include arbitrary files via a .. (dot dot) and trailing %00 (NULL) byte in the (1) template and (2) page parameters in (a) index.php, and the (3) language parameter in (b) inc/backend_settings.php.

The bug was discovered 03/07/2006. The weakness was released 03/09/2006 by tzitaroth (Website). The advisory is shared at secunia.com. This vulnerability is known as CVE-2006-1114 since 03/09/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

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:index.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 21024 (Loudblog < 0.42 template Parameter Traversal), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

Upgrading to version 0.42 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (25103), Tenable (21024), SecurityFocus (BID 17023†), OSVDB (23743†) and Secunia (SA19172†). Entry connected to this vulnerability is available at VDB-29100. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Path traversal
CWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 21024
Nessus Name: Loudblog < 0.42 template Parameter Traversal
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Loudblog 0.42

Timelineinfo

03/07/2006 🔍
03/07/2006 +0 days 🔍
03/07/2006 +0 days 🔍
03/08/2006 +1 days 🔍
03/08/2006 +0 days 🔍
03/09/2006 +1 days 🔍
03/09/2006 +0 days 🔍
03/09/2006 +0 days 🔍
04/04/2006 +26 days 🔍
03/12/2015 +3264 days 🔍
06/16/2019 +1557 days 🔍

Sourcesinfo

Advisory: secunia.com⛔
Researcher: tzitaroth
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-1114 (🔍)
GCVE (CVE): GCVE-0-2006-1114
GCVE (VulDB): GCVE-100-29101
X-Force: 25103
SecurityFocus: 17023 - Loudblog Multiple Input Validation Vulnerabilities
Secunia: 19172 - Loudblog Multiple Vulnerabilities, Moderately Critical
OSVDB: 23743 - Loudblog index.php "dot dot" directory traversal
Vulnerability Center: 10917 - Loudblog Remote Directory Traversal Vulnerabilities, High
Vupen: ADV-2006-0878

See also: 🔍

Entryinfo

Created: 03/12/2015 12:19
Updated: 06/16/2019 09:38
Changes: 03/12/2015 12:19 (76), 06/16/2019 09:38 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!