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.

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.

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.

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.

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.

Vulnerability/
CVE-2019-7860

high

7.5

CWE

338

25/6/2019

2/8/2019

4/8/2024

CVE-2019-7860: Weak RNG

First published: Tue 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.

Credit: psirt@adobe.com psirt@adobe.com

Affected Software	Affected Version	How to fix
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	>=2.1.0<2.1.18
Magento	>=2.2.0<2.2.9
Magento	>=2.3.0<2.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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

collector/friends-of-php
agent/type
agent/author
agent/first-publish-date
collector/github-advisory-latest
source/GitHub
alias/GHSA-8v9h-m7pj-hx7c
alias/CVE-2019-7860
agent/software-canonical-lookup
agent/weakness
agent/references
agent/severity
agent/softwarecombine
agent/description
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/trending
agent/source
agent/tags
collector/nvd-cve
source/NVD
agent/software-canonical-lookup-request
collector/nvd-index
package-manager/composer
vendor/magento
canonical/magento
version/magento/2.1.0
version/magento/2.2.0
version/magento/2.3.0

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.

Frequently Asked Questions

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