First published: Tue Oct 08 2019(Updated: )
An insufficient logging and monitoring 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. Failure to track admin actions related to design configuration could lead to repudiation attacks.
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 | |
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-8124 is categorized as a medium severity vulnerability due to its potential for repudiation attacks.
To fix CVE-2019-8124, you need to upgrade to Magento versions 2.1.19, 2.2.10, or 2.3.3.
CVE-2019-8124 affects Magento 2.1 prior to 2.1.19, 2.2 prior to 2.2.10, and 2.3 prior to 2.3.3.
CVE-2019-8124 is an insufficient logging and monitoring vulnerability.
The risks associated with CVE-2019-8124 include the potential for unauthorized changes to design configurations and subsequent repudiation attacks.