Oxid eSales 4.10.6 DB Abstraction Layer core/oxconfig.php getRequestParameter synchoxid sql injection

Summaryinfo

A vulnerability marked as critical has been reported in Oxid eSales 4.10.6. This issue affects the function oxConfig::getRequestParameter of the file core/oxconfig.php of the component DB Abstraction Layer. The manipulation of the argument synchoxid as part of Parameter leads to sql injection. This vulnerability is traded as CVE-2018-20715. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Oxid eSales 4.10.6 and classified as critical. This issue affects the function oxConfig::getRequestParameter of the file core/oxconfig.php of the component DB Abstraction Layer. The manipulation of the argument synchoxid as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The DB abstraction layer of OXID eSales 4.10.6 is vulnerable to SQL injection via the oxid or synchoxid parameter to the oxConfig::getRequestParameter() method in core/oxconfig.php.

The bug was discovered 01/17/2019. The weakness was shared 01/15/2019 (Website). The advisory is shared at demo.ripstech.com. The identification of this vulnerability is CVE-2018-20715 since 01/15/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:core/oxconfig.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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Oxid

Name

• eSales

Version

• 4.10.6

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