CVE Vulnerabilities

CVE-2024-39410

Cross-Site Request Forgery (CSRF)

Published: Aug 14, 2024 | Modified: Sep 16, 2024
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Adobe Commerce versions 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could allow an attacker to bypass security features and perform minor integrity changes on behalf of a user. The vulnerability could be exploited by tricking a victim into clicking a link or loading a page that submits a malicious request. Exploitation of this issue does not require user interaction.

Weakness

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Affected Software

Name Vendor Start Version End Version
Commerce Adobe * 2.4.3 (including)
Commerce Adobe 2.4.4 (including) 2.4.4 (including)
Commerce Adobe 2.4.4-p1 (including) 2.4.4-p1 (including)
Commerce Adobe 2.4.4-p2 (including) 2.4.4-p2 (including)
Commerce Adobe 2.4.4-p3 (including) 2.4.4-p3 (including)
Commerce Adobe 2.4.4-p4 (including) 2.4.4-p4 (including)
Commerce Adobe 2.4.4-p5 (including) 2.4.4-p5 (including)
Commerce Adobe 2.4.4-p6 (including) 2.4.4-p6 (including)
Commerce Adobe 2.4.4-p7 (including) 2.4.4-p7 (including)
Commerce Adobe 2.4.4-p8 (including) 2.4.4-p8 (including)
Commerce Adobe 2.4.4-p9 (including) 2.4.4-p9 (including)
Commerce Adobe 2.4.5 (including) 2.4.5 (including)
Commerce Adobe 2.4.5-p1 (including) 2.4.5-p1 (including)
Commerce Adobe 2.4.5-p2 (including) 2.4.5-p2 (including)
Commerce Adobe 2.4.5-p3 (including) 2.4.5-p3 (including)
Commerce Adobe 2.4.5-p4 (including) 2.4.5-p4 (including)
Commerce Adobe 2.4.5-p5 (including) 2.4.5-p5 (including)
Commerce Adobe 2.4.5-p6 (including) 2.4.5-p6 (including)
Commerce Adobe 2.4.5-p7 (including) 2.4.5-p7 (including)
Commerce Adobe 2.4.5-p8 (including) 2.4.5-p8 (including)
Commerce Adobe 2.4.6 (including) 2.4.6 (including)
Commerce Adobe 2.4.6-p1 (including) 2.4.6-p1 (including)
Commerce Adobe 2.4.6-p2 (including) 2.4.6-p2 (including)
Commerce Adobe 2.4.6-p3 (including) 2.4.6-p3 (including)
Commerce Adobe 2.4.6-p4 (including) 2.4.6-p4 (including)
Commerce Adobe 2.4.6-p5 (including) 2.4.6-p5 (including)
Commerce Adobe 2.4.6-p6 (including) 2.4.6-p6 (including)
Commerce Adobe 2.4.7 (including) 2.4.7 (including)
Commerce Adobe 2.4.7-b1 (including) 2.4.7-b1 (including)
Commerce Adobe 2.4.7-b2 (including) 2.4.7-b2 (including)
Commerce Adobe 2.4.7-p1 (including) 2.4.7-p1 (including)

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]

References