YaPiG 0.92b/0.93u/0.94u mkdir upload.php 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 has been found in YaPiG 0.92b/0.93u/0.94u and classified as problematic. This issue affects some unknown processing of the file upload.php of the component mkdir. The manipulation of the argument dir leads to path traversal. This vulnerability is traded as CVE-2005-1884. Furthermore, there is an exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in YaPiG 0.92b/0.93u/0.94u. It has been rated as problematic. This issue affects an unknown part of the file upload.php of the component mkdir. The manipulation of the argument dir with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity, and availability. The summary by CVE is:

Directory traversal vulnerability in the (1) rmdir or (2) mkdir commands in upload.php in YaPiG 0.92b, 0.93u and 0.94u allows remote attackers to create or delete arbitrary directories via a .. (dot dot) in the dir parameter.

The bug was discovered 05/29/2005. The weakness was shared 06/04/2005 (Website). The advisory is shared at secwatch.org. The identification of this vulnerability is CVE-2005-1884 since 06/08/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:upload.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 18523 (YaPiG < 0.95b Multiple Vulnerabilities), 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 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (20901), Tenable (18523), SecurityFocus (BID 13877†), OSVDB (17120†) and Secunia (SA15600†). The entries VDB-25470, VDB-25468, VDB-25467 and VDB-25433 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

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: 18523
Nessus Name: YaPiG < 0.95b Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 18523
OpenVAS Name: YaPiG Multiple Flaws
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/29/2005 🔍
06/04/2005 +6 days 🔍
06/04/2005 +0 days 🔍
06/05/2005 +0 days 🔍
06/06/2005 +1 days 🔍
06/06/2005 +0 days 🔍
06/06/2005 +0 days 🔍
06/06/2005 +0 days 🔍
06/08/2005 +1 days 🔍
06/09/2005 +1 days 🔍
06/17/2005 +8 days 🔍
10/11/2005 +116 days 🔍
03/11/2015 +3438 days 🔍
06/10/2019 +1552 days 🔍

Sourcesinfo

Advisory: secwatch.org
Status: Not defined

CVE: CVE-2005-1884 (🔍)
GCVE (CVE): GCVE-0-2005-1884
GCVE (VulDB): GCVE-100-25469
X-Force: 20901
SecurityFocus: 13877 - YaPiG Upload.PHP Directory Traversal Vulnerability
Secunia: 15600 - YaPiG Multiple Vulnerabilities, Highly Critical
OSVDB: 17120 - YaPiG upload.php dir Variable Arbitrary Directory Manipulation
SecurityTracker: 1014103
Vulnerability Center: 9381 - YaPiG Directory Traversal via the Upload.php Script, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/11/2015 11:41
Updated: 06/10/2019 10:41
Changes: 03/11/2015 11:41 (84), 06/10/2019 10:41 (1)
Complete: 🔍
Cache ID: 216:131: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!