First published: Tue Oct 08 2019(Updated: )
A remote code execution vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user with privileges to modify product catalogs can trigger PHP file inclusion through a crafted XML file that specifies product design update.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/product-community-edition | >=2.2<2.2.10>=2.3<2.3.2-p2 | |
composer/magento/community-edition | >=2.3.0<2.3.2-p2 | 2.3.2-p2 |
composer/magento/community-edition | >=2.2.0<2.2.10 | 2.2.10 |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.2.0<2.2.10 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | >=2.3.0<2.3.2 | |
CentOS Libgcc | =2.3.2 | |
CentOS Libgcc | =2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-8154 has a high severity rating due to its potential for remote code execution.
To mitigate CVE-2019-8154, upgrade your Magento installation to version 2.2.10 or 2.3.3 and above.
CVE-2019-8154 affects Magento 2.2 versions prior to 2.2.10 and Magento 2.3 versions prior to 2.3.3 or 2.3.2-p1.
No, exploitation of CVE-2019-8154 requires an authenticated user with the ability to modify product catalogs.
CVE-2019-8154 facilitates a remote code execution attack through PHP file inclusion from a crafted XML file.