Skip to content

PrestaShop eval injection possible if shop vulnerable to SQL injection

Critical severity GitHub Reviewed Published Jul 25, 2022 in PrestaShop/PrestaShop • Updated Jan 27, 2023

Package

composer prestashop/prestashop (Composer)

Affected versions

>= 1.6.0.10, < 1.7.8.7

Patched versions

1.7.8.7

Description

Impact

Eval injection possible if the shop is vulnerable to an SQL injection.

Patches

The problem is fixed in version 1.7.8.7

Workarounds

Delete the MySQL Smarty cache feature by removing these lines in the file config/smarty.config.inc.php lines 43-46 (PrestaShop 1.7) or 40-43 (PrestaShop 1.6):

if (Configuration::get('PS_SMARTY_CACHING_TYPE') == 'mysql') {
    include _PS_CLASS_DIR_.'Smarty/SmartyCacheResourceMysql.php';
    $smarty->caching_type = 'mysql';
}

References

@atomiix atomiix published to PrestaShop/PrestaShop Jul 25, 2022
Published to the GitHub Advisory Database Jul 29, 2022
Reviewed Jul 29, 2022
Published by the National Vulnerability Database Aug 1, 2022
Last updated Jan 27, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.208%
(59th percentile)

Weaknesses

CVE ID

CVE-2022-31181

GHSA ID

GHSA-hrgx-p36p-89q4

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.