Skip to content

GHSA-q628-54wg-4r5q CVE-2024-39398

Magento does not properly restrict excessive authentication attempts

High Packagist
Severity
7.4 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.86%
Chance of exploitation in the next 30 days. Higher than 58.51% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-307 Improper Restriction of Excessive Authentication Attempts
Fix
2.4.7-p2
Upgrade magento/community-edition to this version or later

Description

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

Affected versions

Packagist

PackageVulnerableFixed in
magento/community-edition
>= 2.4.7-beta1, < 2.4.7-p2
2.4.7-p2
magento/community-edition
>= 2.4.6-p1, < 2.4.6-p7
2.4.6-p7
magento/community-edition
>= 2.4.5-p1, < 2.4.5-p9
2.4.5-p9
magento/community-edition
>= 2.4.4-p1, < 2.4.4-p10
2.4.4-p10
magento/community-edition 1 listed versions No fix yet
magento/community-edition 1 listed versions No fix yet
magento/community-edition 1 listed versions No fix yet
magento/community-edition 1 listed versions No fix yet
magento/project-community-edition
<= 2.0.2
No fix yet

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

magento/community-edition Packagist → 2.4.7-p2

composer
composer require magento/community-edition:^2.4.7-p2

Severity breakdown

CVSS 3.1 7.4

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-307: Improper Restriction of Excessive Authentication Attempts

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

How to prevent it
  • Architecture and Design: Common protection mechanisms include: Disconnecting the user after a small number of failed attempts Implementing a timeout Locking out a targeted account Requiring a computational task on the user's part.
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-wh92-6q6g-px7j
Magento Community Edition Improper Input Validation vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-m8cj-3v68-3cxj
Magento Open Source affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-f8fv-f786-9933
Magento improper input validation vulnerability
Critical Known exploited Also affects magento/community-edition
GHSA-qvwr-p3hj-j6jf
Magento vulnerable to privilege escalation due to incorrect authorization
Medium Also affects magento/community-edition
GHSA-pcrx-r49h-x2w5
Magento vulnerable to stored Cross-Site Scripting (XSS)
Medium Also affects magento/community-edition
GHSA-r355-75hw-r8jf
Magento allows incorrect authorization
Medium Also affects magento/community-edition
GHSA-2768-5wmv-cfff
Magento vulnerable to stored Cross-Site Scripting (XSS)
High Also affects magento/community-edition
GHSA-69x9-xp2j-w8g8
Magento provides incorrect authorization through a security feature bypass
High Also affects magento/community-edition
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor