First published: Tue Jun 25 2019(Updated: )
A cryptographic flaw in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9 and Magento 2.3 prior to 2.3.2 resulted in storage of sensitive information with an algorithm that is insufficiently resistant to brute force attacks.
Credit: 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 |
CentOS Libgcc | >=2.1.0<2.1.18 | |
CentOS Libgcc | >=2.2.0<2.2.9 | |
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-7858 is considered to have a high severity due to its potential for brute force attacks on sensitive information.
CVE-2019-7858 affects Magento 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2.
To fix CVE-2019-7858, upgrade to Magento versions 2.1.18, 2.2.9, or 2.3.2 or later.
CVE-2019-7858 can lead to the storage of sensitive user credentials in an insecure manner.
Yes, Magento has released security updates that address CVE-2019-7858 in the specified versions.