First published: Tue Oct 08 2019(Updated: )
A remote code execution vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. An authenticated admin user with import product privileges can delete files through bulk product import and inject code into XSLT file. The combination of these manipulations can lead to remote code execution.
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.3 | 2.3.3 |
composer/magento/community-edition | >=2.2.0<2.2.10 | 2.2.10 |
composer/magento/community-edition | >=2.1.0<2.1.19 | 2.1.19 |
CentOS Libgcc | >=2.1.0<2.1.19 | |
CentOS Libgcc | >=2.1.0<2.1.19 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-8119 is classified as a critical vulnerability due to its potential for remote code execution.
CVE-2019-8119 affects Magento 2.1 versions prior to 2.1.19, Magento 2.2 prior to 2.2.10, and Magento 2.3 prior to 2.3.3.
To fix CVE-2019-8119, upgrade Magento to version 2.3.3, 2.2.10, or 2.1.19 or later.
CVE-2019-8119 enables an authenticated administrator to perform remote code execution through bulk product import.
Only authenticated admin users with import product privileges can exploit CVE-2019-8119.