Skip to content
Fencer Intel
high 7.4

CVE-2024-39398 json

OTP 2FA can be bruteforced

published 2y ago modified 4mo ago also GHSA-q628-54wg-4r5q , EUVD-2024-37948

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

Adobe Commerce versions 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 and earlier are affected by an Improper Restriction of Excessive Authentication Attempts vulnerability that could result in a security feature bypass. An attacker could exploit this vulnerability to perform brute force attacks and potentially gain unauthorized access to accounts. Exploitation of this issue does not require user interaction, but attack complexity is high.

Patch / fix

  • packagist magento/community-edition 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, 2.4.7-p2

Is CVE-2024-39398 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/project-community-edition
<=2.0.2
no fix listed
packagist magento/community-edition
>=2.4.7-beta1, <2.4.7-p2
>=2.4.6-p1, <2.4.6-p7
>=2.4.5-p1, <2.4.5-p9
>=2.4.4-p1, <2.4.4-p10
1 listed version
2.4.7-p2
2.4.6-p7
2.4.5-p9
2.4.4-p10

Affected products

  • Adobe Adobe Commerce
  • adobe commerce

Classification

Weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts

References

Sources

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.