[CVE-2024-25848] Improper neutralization of SQL parameter in Team Ever – Ever Ultimate SEO module for PrestaShop

PrestaShop Security Advisory

In the module “Ever Ultimate SEO” (everpsseo) from Team Ever for PrestaShop, a guest can perform SQL injection in affected versions.

Summary

  • CVE ID: CVE-2024-25848
  • Published at: 2024-03-05
  • Platform: PrestaShop
  • Product: everpsseo
  • Impacted release: <= 7.13.4 for PrestaShop 1.6 (7.13.5 fix the vulnerability) & <= 8.1.2 for PrestaShop 1.7+ (8.1.3 fixed the vulnerability)
  • Product author: Team Ever
  • Weakness: CWE-89
  • Severity: critical (9.8)

Description

The method EverPsSeo::hookHeader() has sensitive SQL calls that can be executed with a trivial http call and exploited to forge a SQL injection.

This exploit uses a PrestaShop Hook stappled on all pages and most attackers can conceal the attack during the exploit, so you will never know within your conventional frontend logs that it exploits this vulnerability. You will only see “POST /” inside your conventional frontend logs. Activating the AuditEngine of mod_security (or similar) is the only way to get data to confirm this exploit.

CVSS base metrics

  • Attack vector: network
  • Attack complexity: low
  • Privilege required: none
  • User interaction: none
  • Scope: unchanged
  • Confidentiality: high
  • Integrity: high
  • Availability: high

Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Possible malicious usage

  • Obtain admin access
  • Remove data from the associated PrestaShop
  • Copy/paste data from sensitive tables to FRONT to expose tokens and unlock admins’s ajax scripts
  • Rewrite SMTP settings to hijack emails

Patch from 7.8.15

--- 7.8.15/modules/everpsseo/everpsseo.php
+++ XXXXXX/modules/everpsseo/everpsseo.php
...
                        FROM '._DB_PREFIX_.'meta
-                       WHERE page = "'.(string)$controller_name.'"'
+                       WHERE page = "'.pSQL($controller_name).'"'
                    );
...
                        FROM '._DB_PREFIX_.'meta
-                       WHERE page = "'.(string)$controller_name.'"'
+                       WHERE page = "'.pSQL($controller_name).'"'
                    );
...
                        FROM '._DB_PREFIX_.'meta
-                       WHERE page = "'.(string)$controller_name.'"'
+                       WHERE page = "'.pSQL($controller_name).'"'
                    );
...

Other recommendations

  • It’s recommended to upgrade to the latest version of the module everpsseo.
  • To help improve the security of your PrestaShop installation, we recommend upgrading to the latest version. One of the benefits of upgrading is that it will disable the use of multiquery executions (separated by semicolons). However, please be aware that this will not protect your shop against SQL injection attacks that use the UNION clause to steal data. Additionally, it’s important to note that PrestaShop includes a function called pSQL, which includes a strip_tags function. This helps protect your shop against Stored XSS (also known as XSS T2) of Category 1. If a pSQL function is missing, it could potentially expose your project to critical Stored XSS vulnerabilities due to edge cases. Therefore, it’s crucial to ensure that all relevant functions are properly implemented and used consistently throughout your project.
  • Change the default database prefix ps_ with a new longer, arbitrary prefix. Nevertheless, be warned that this is useless against blackhats with DBA senior skills because of a design vulnerability in DBMS
  • Activate OWASP 942’s rules on your WAF (Web application firewall), be warned that you will probably break your backoffice and you will need to pre-configure some bypasses against this set of rules.

Timeline

DateAction
2022-09-20Issue discovered during a code review by TouchWeb.fr
2023-09-20Friends of Presta contact author to confirm versions scope
2023-10-30Contact PrestaShop Addons security Team to confirm version scope
2024-02-22Received CVE ID
2024-03-05Publish this security advisory

Team Ever thanks TouchWeb for its courtesy and its help after the vulnerability disclosure.

READ MORE

Leave a Reply

Your email address will not be published. Required fields are marked *