FarsiNews 2.1/2.1 Beta2/2.5/2.5.3 Error Message index.php Archive path traversal

Summaryinfo

A vulnerability was found in FarsiNews 2.1/2.1 Beta2/2.5/2.5.3. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file index.php of the component Error Message Handler. The manipulation of the argument Archive results in path traversal. This vulnerability is known as CVE-2006-1823. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in FarsiNews 2.1/2.1 Beta2/2.5/2.5.3. Affected is some unknown processing of the file index.php of the component Error Message Handler. The manipulation of the argument archive with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, and integrity. CVE summarizes:

Directory traversal vulnerability in FarsiNews 2.5.3 Pro and earlier allows remote attackers to obtain the installation path via ".." sequences in the archive parameter to index.php, which leaks the full pathname in an error message.

The weakness was published 04/18/2006 (Website). The advisory is shared for download at vupen.com. This vulnerability is traded as CVE-2006-1823 since 04/17/2006. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. 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 proof-of-concept. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Secunia (SA19648†) and SecurityTracker (ID 1015943†). Similar entry is available at VDB-29699. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• FarsiNews

Version

• 2.1
• 2.1 Beta2
• 2.5
• 2.5.3

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion