BibORB 1.3.2 index.php database_name path traversal

Summaryinfo

A vulnerability was found in BibORB 1.3.2. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the file index.php. The manipulation of the argument database_name leads to path traversal. This vulnerability is referenced as CVE-2005-0253. Furthermore, an exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in BibORB 1.3.2. This issue affects an unknown code block of the file index.php. The manipulation of the argument database_name 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 availability. The summary by CVE is:

Directory traversal vulnerability in index.php for BibORB 1.3.2, and possibly earlier versions, allows remote attackers to delete arbitrary files via a Delete action and .. (dot dot) sequences in the database_name parameter.

The weakness was published 05/02/2005 by Patrick (Website). The advisory is shared at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2005-0253 since 02/09/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 public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

The exploit is available at exploit-db.com. 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 Exploit-DB (25120) and SecurityFocus (BID 12583†). Similar entries are available at VDB-24366, VDB-24364 and VDB-24363. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• BibORB

Version

• 1.3.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

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

Discussion