TinyButStrong 3.4.0 script path traversal

Summaryinfo

A vulnerability has been found in TinyButStrong 3.4.0 and classified as problematic. This vulnerability affects unknown code. This manipulation of the argument script causes path traversal. This vulnerability is registered as CVE-2009-1653. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in TinyButStrong 3.4.0. Affected by this vulnerability is an unknown part. The manipulation of the argument script 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. The summary by CVE is:

Directory traversal vulnerability in examples/tbs_us_examples_0view.php in TinyButStrong 3.4.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the script parameter.

The weakness was published 05/16/2009 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2009-1653 since 05/16/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

A public exploit has been developed by ahmadbady and been published before and not just after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.

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 X-Force (50506) and Exploit-DB (8667). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• TinyButStrong

Version

• 3.4.0

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