JquickContact 1.3.2.2.1 on Joomla Request sql injection

Summaryinfo

A vulnerability marked as critical has been reported in JquickContact 1.3.2.2.1 on Joomla. This vulnerability affects unknown code. Performing a manipulation as part of Request results in sql injection. This vulnerability was named CVE-2018-5983. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in JquickContact 1.3.2.2.1 on Joomla (Joomla Component). It has been classified as critical. This affects an unknown code. 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 JquickContact 1.3.2.2.1 component for Joomla! via a task=refresh&sid= request.

The bug was discovered 02/16/2018. The weakness was presented 02/17/2018 as EDB-ID 44118 as not defined exploit (Exploit-DB). It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-5983 since 01/22/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. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

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 (44118). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Joomla Component

Name

• JquickContact

Version

• 1.3.2.2.1

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