DT Register Extension 3.2.7 on Joomla Request sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in DT Register Extension 3.2.7 on Joomla. Affected is an unknown function. Performing a manipulation as part of Request results in sql injection. This vulnerability is identified as CVE-2018-6584. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in DT Register Extension 3.2.7 on Joomla (Joomla Component). It has been classified as critical. This affects an unknown functionality. The manipulation as part of a Request 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 exists in the DT Register 3.2.7 component for Joomla! via a task=edit&id= request.

The bug was discovered 02/16/2018. The weakness was released 02/17/2018 as EDB-ID 44108 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-6584 since 02/02/2018. 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 are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

After immediately, there has been an exploit disclosed. The exploit is shared for download 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 1 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 vulnerability database at Exploit-DB (44108). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Joomla Component

Name

• DT Register Extension

Version

• 3.2.7

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