Sbuilder CMS S.Builder up to 3.7 index.php code injection

Summaryinfo

A vulnerability has been found in Sbuilder CMS S.Builder up to 3.7 and classified as critical. This affects an unknown part of the file index.php. This manipulation causes code injection. The identification of this vulnerability is CVE-2009-4887. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Sbuilder CMS S.Builder up to 3.7 (Content Management System). It has been declared as critical. Affected by this vulnerability is an unknown part of the file index.php. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

PHP remote file inclusion vulnerability in index.php in CMS S.Builder 3.7 and earlier, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in a binn_include_path cookie. NOTE: this can also be leveraged to include and execute arbitrary local files.

The weakness was shared 06/11/2010 (Website). It is possible to read the advisory at milw0rm.com. This vulnerability is known as CVE-2009-4887 since 06/11/2010. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

A public exploit has been developed by cr0w and been published even before and not 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 459 days. During that time the estimated underground price was around $0-$5k. 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 X-Force (49139), Exploit-DB (8172) and SecurityFocus (BID 34037†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Sbuilder

Name

• CMS S.Builder

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion