CVE-2019-8118 json
Magento 2 Community Edition Weak Cryptography
published 7y ago modified 4mo ago also GHSA-hmch-9947-82rj , EUVD-2022-4173
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist magento/community-edition 2.1.19, 2.2.10, 2.3.3
- magento magento 2.1.19, 2.2.10, 2.3.2
Is CVE-2019-8118 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.1.0, <2.1.19 >=2.2.0, <2.2.10 >=2.3.0, <2.3.3 |
2.1.19 2.2.10 2.3.3 |
Affected products
- Adobe Systems Incorporated Magento 2
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
magento.com
/security/patches/magento-2.3.3-and-2.2.10-security-update
web, patch, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-8118
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8118.yaml
web
-
github.com
/magento/magento2
package
-
web.archive.org
/web/20220121051105/https://magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update
web
Sources
- CVE List CVE-2019-8118
- GitHub Advisory GHSA-hmch-9947-82rj
- NVD CVE-2019-8118
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.