CVE-2019-7860: Magento 2 Community Edition Weak PRNG

Published Jun 25, 2019
·
Updated

A cryptographically weak pseudo-rando number generator is used in multiple security relevant contexts in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2.

Other sources

PRODSECBUG-2174: Use of insufficiently random values in multiple security relevant contexts

Affected Software

13 affected componentsFixes available
composer/magento/product-community-edition>=2.1, <2.1.18, >=2.2, <2.2.9, >=2.3, <2.3.2
composer/magento/community-edition>=2.3.0<2.3.2
2.3.2
composer/magento/community-edition>=2.2.0<2.2.9
2.2.9
composer/magento/community-edition>=2.1.0<2.1.18
2.1.18
Magento Magento>=2.1.0<2.1.18
Magento Magento>=2.2.0<2.2.9
Magento Magento>=2.3.0<2.3.2
composer/magento/community-edition>=2.3.0, <2.3.2
2.3.2
composer/magento/community-edition>=2.2.0, <2.2.9
2.2.9
composer/magento/community-edition>=2.1.0, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.1, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.2, <2.2.9
2.2.9
composer/magento/product-community-edition>=2.3, <2.3.2
2.3.2

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.2
  2. Upgrade

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

    Fixed in 2.2.9
  3. Upgrade

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

    Fixed in 2.1.18
  4. Upgrade

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

    Fixed in 2.1.18
  5. Upgrade

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

    Fixed in 2.2.9
  6. Upgrade

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

    Fixed in 2.3.2

Event History

Jun 25, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Aug 2, 2019
CVE Published
via MITRE·09:13 PM
Data Sourced
via MITRE·09:13 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·04:52 PM
Data Sourced
via GitHub·04:52 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-7860?

CVE-2019-7860 is considered a moderate severity vulnerability due to the use of a cryptographically weak pseudo-random number generator.

2

What products are affected by CVE-2019-7860?

CVE-2019-7860 affects Magento 2.1 versions prior to 2.1.18, Magento 2.2 versions prior to 2.2.9, and Magento 2.3 versions prior to 2.3.2.

3

How do I fix CVE-2019-7860?

To fix CVE-2019-7860, upgrade your Magento installation to version 2.1.18, 2.2.9, or 2.3.2, depending on your current version.

4

What are the potential consequences of CVE-2019-7860?

The consequences of CVE-2019-7860 include potential exposure to security risks due to insufficient randomness in cryptographic operations.

5

Is there a patch for CVE-2019-7860?

Yes, security updates have been released that can be applied to patch CVE-2019-7860 for the affected versions of Magento.

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