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. Dependency injection through Symphony framework allows service identifiers to be derived from user controlled data, which 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<2.3.2-p2 | 2.3.2-p2 |
composer/magento/community-edition | >=2.2<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-8135 is rated as a critical vulnerability due to its potential for remote code execution.
To fix CVE-2019-8135, users should upgrade to Magento version 2.2.10 or higher and version 2.3.3 or higher.
CVE-2019-8135 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.
CVE-2019-8135 is a remote code execution vulnerability due to dependency injection issues in the Symphony framework.
If exploited, CVE-2019-8135 could allow attackers to execute arbitrary code on the server running affected Magento versions.