First published: Tue Oct 08 2019(Updated: )
An insufficient logging and monitoring vulnerability exists in Magento 1 prior to 1.9.4.3 and 1.14.4.3, Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. The logging feature required for effective monitoring did not contain sufficent data to effectively track configuration changes.
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/magento1ce | >=1<1.9.4.3 | |
composer/magento/magento1ee | >=1<1.14.4.3 | |
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 | <1.9.3.4 | |
CentOS Libgcc | <1.14.4.3 | |
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-8123 is classified as a medium severity vulnerability due to insufficient logging and monitoring.
To mitigate CVE-2019-8123, upgrade to Magento versions 1.9.4.4 or 1.14.4.4 for Magento 1, and 2.1.19, 2.2.10, or 2.3.3 for Magento 2.
CVE-2019-8123 affects Magento 1 versions prior to 1.9.4.3 and 1.14.4.3, as well as Magento 2.1 versions before 2.1.19, 2.2 versions before 2.2.10, and 2.3 versions before 2.3.3.
CVE-2019-8123 involves a lack of necessary data in logging features, which hampers the effectiveness of tracking configuration changes.
Yes, patches addressing CVE-2019-8123 are included in the aforementioned Magento version upgrades.