Springsignage Xibo 1.4.2 index.php displayid sql injection

Summaryinfo

A vulnerability identified as critical has been detected in Springsignage Xibo 1.4.2. Affected by this issue is some unknown functionality of the file index.php. Performing a manipulation of the argument displayid results in sql injection. This vulnerability was named CVE-2013-4887. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in Springsignage Xibo 1.4.2. This affects some unknown functionality of the file index.php. The manipulation of the argument displayid with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in index.php in Digital Signage Xibo 1.4.2 allows remote attackers to execute arbitrary SQL commands via the displayid parameter.

The weakness was presented 01/29/2014 by Jacob Holcomb with Independent Security Evaluators (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2013-4887 since 07/22/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

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 (86777) and SecurityFocus (BID 62071†). See VDB-66245 and VDB-66244 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Springsignage

Name

• Xibo

Version

• 1.4.2

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