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 user with privileges to create products can craft custom layout update and use import product functionality to enable 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-8122 is classified as a critical remote code execution vulnerability affecting specific versions of Magento.
To fix CVE-2019-8122, upgrade Magento to version 2.1.19, 2.2.10, or 2.3.3 or later.
CVE-2019-8122 affects authenticated users with privileges to create products on Magento versions prior to the recommended fixed versions.
Attackers exploiting CVE-2019-8122 can perform remote code execution, potentially compromising the security of the Magento installation.
No, CVE-2019-8122 is only present in specific affected versions of Magento prior to the security updates.