Docebo DoceboLMS 2.0.4/2.0.5/4.0/4.0.4 lib/lib.iotask.php save_connection sql injection

Summaryinfo

A vulnerability was found in Docebo DoceboLMS 2.0.4/2.0.5/4.0/4.0.4 and classified as critical. This affects the function save_connection in the library lib/lib.iotask.php. Executing a manipulation can lead to sql injection. The identification of this vulnerability is CVE-2011-5135. The attack may be launched remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability was found in Docebo DoceboLMS 2.0.4/2.0.5/4.0/4.0.4. It has been declared as critical. This vulnerability affects the function save_connection in the library lib/lib.iotask.php. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Multiple SQL injection vulnerabilities in the save_connection function in lib/lib.iotask.php in the iotask module in DoceboLMS 4.0.4 and earlier allow remote authenticated users with admin or teacher privileges to execute arbitrary SQL commands via the (1) coursereportuiconfig[name] or (2) coursereportuiconfig[description] parameters to index.php.

The weakness was shared 08/30/2012 (Website). The advisory is available at twitter.com. This vulnerability was named CVE-2011-5135 since 08/30/2012. The attack can be initiated remotely. A single authentication is needed for exploitation. Technical details and also a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:lib/lib.iotask.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 (71720), Exploit-DB (18224) and OSVDB (77632†). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Docebo

Name

• DoceboLMS

Version

• 2.0.4
• 2.0.5
• 4.0
• 4.0.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion