First published: Tue Oct 08 2019(Updated: )
Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 uses weak cryptographic function to store the failed login attempts for customer accounts.
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/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 | >=2.1.0<2.1.19 | |
CentOS Libgcc | >=2.1.0<2.1.19 | |
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 | |
CentOS Libgcc | =2.3.2 | |
CentOS Libgcc | =2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-8118 has a high severity due to the use of weak cryptographic functions to store failed login attempts.
To fix CVE-2019-8118, upgrade to Magento 2.1.19, 2.2.10, or 2.3.3 or later.
CVE-2019-8118 affects Magento 2.1 versions prior to 2.1.19, 2.2 versions prior to 2.2.10, and 2.3 versions prior to 2.3.3.
CVE-2019-8118 specifically impacts customer accounts due to improper storage of login attempt data.
Yes, CVE-2019-8118 compromises the security of customer passwords stored in clear text after failed login attempts.