CVE-2019-8124: Magento 2 Community Edition Insufficient Logging

Published Oct 8, 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.

Other sources

Magento 2 Community Edition Insufficient Logging

— Packagist

PRODSECBUG-2444: Missing logs of configuration changes related to design update

Affected Software

17 affected componentsFixes available
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
Magento Magento>=2.1.0<2.1.19
Magento Magento>=2.1.0<2.1.19
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.3.0<2.3.2
Magento Magento>=2.3.0<2.3.2
Magento Magento=2.3.2
Magento Magento=2.3.2
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
composer/magento/product-community-edition>=2.2, <2.2.10
2.2.10
composer/magento/product-community-edition>=2.3, <2.3.2-p2
2.3.2-p2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.3
  2. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  3. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.1.19
  4. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  5. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p2
  6. Upgrade

    Upgrade Magento 2.1 to a version that resolves this vulnerability.

    Fixed in 2.1.19
  7. Upgrade

    Upgrade Magento 2.2 to a version that resolves this vulnerability.

    Fixed in 2.2.10
  8. Upgrade

    Upgrade Magento 2.3 to a version that resolves this vulnerability.

    Fixed in 2.3.3

Event History

Oct 8, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Nov 5, 2019
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityAffected Software
May 24, 2022
Advisory Published
via GitHub·05:00 PM
Data Sourced
via GitHub·05:00 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-8124?

CVE-2019-8124 is categorized as a medium severity vulnerability due to its potential for repudiation attacks.

2

How do I fix CVE-2019-8124?

To fix CVE-2019-8124, you need to upgrade to Magento versions 2.1.19, 2.2.10, or 2.3.3.

3

Which versions of Magento are affected by CVE-2019-8124?

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.

4

What type of vulnerability is CVE-2019-8124?

CVE-2019-8124 is an insufficient logging and monitoring vulnerability.

5

What are the risks associated with CVE-2019-8124?

The risks associated with CVE-2019-8124 include the potential for unauthorized changes to design configurations and subsequent repudiation attacks.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203