GForge 3.1/3.2/3.3/3.21 controller.php dir_name 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.1$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in GForge 3.1/3.2/3.3/3.21. Affected by this issue is some unknown functionality of the file controller.php. Executing a manipulation of the argument dir_name can lead to path traversal. This vulnerability appears as CVE-2005-0299. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in GForge 3.1/3.2/3.3/3.21 (Project Management Software). It has been declared as problematic. This vulnerability affects an unknown function of the file controller.php. The manipulation of the argument dir_name 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 GForge 3.3 and earlier allows remote attackers to list arbitrary directories via a .. (dot dot) in the (1) dir parameter to controller.php or (2) dir_name parameter to controlleroo.php.

The bug was discovered 01/20/2005. The weakness was presented 05/02/2005 by Jeremy Bae (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2005-0299 since 02/10/2005. The exploitation appears to be easy. 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.

The vulnerability was handled as a non-public zero-day exploit for at least 102 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:controller.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 19187 (FreeBSD : gforge -- directory traversal vulnerability (fe903533-ff96-4c7a-bd3e-4d40efa71897)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l.

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (19187), SecurityFocus (BID 12318†), OSVDB (13088†), SecurityTracker (ID 1012950†) and Vulnerability Center (SBV-6914†). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 19187
Nessus Name: FreeBSD : gforge -- directory traversal vulnerability (fe903533-ff96-4c7a-bd3e-4d40efa71897)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 53001
OpenVAS Name: FreeBSD Ports: gforge
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

01/20/2005 🔍
01/20/2005 +0 days 🔍
01/20/2005 +0 days 🔍
01/20/2005 +0 days 🔍
01/26/2005 +6 days 🔍
02/10/2005 +15 days 🔍
05/02/2005 +81 days 🔍
05/02/2005 +0 days 🔍
06/03/2005 +32 days 🔍
07/13/2005 +40 days 🔍
03/10/2015 +3527 days 🔍
07/01/2021 +2305 days 🔍

Sourcesinfo

Advisory: securityfocus.com
Researcher: Jeremy Bae
Status: Confirmed

CVE: CVE-2005-0299 (🔍)
GCVE (CVE): GCVE-0-2005-0299
GCVE (VulDB): GCVE-100-24388
X-Force: 18988
SecurityFocus: 12318 - GForge Multiple Information Disclosure Vulnerabilities
OSVDB: 13088 - GForge dir and dir_name directory traversal
SecurityTracker: 1012950
Vulnerability Center: 6914 - Gforge \x27controller.php\x27 and \x27controlleroo.php\x27 Directory Content Disclosure, Medium

Entryinfo

Created: 03/10/2015 23:05
Updated: 07/01/2021 17:28
Changes: 03/10/2015 23:05 (72), 05/29/2019 15:52 (10), 07/01/2021 17:28 (3)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!