CVE Vulnerabilities

CVE-2024-20718

Cross-Site Request Forgery (CSRF)

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

Adobe Commerce versions 2.4.6-p3, 2.4.5-p5, 2.4.4-p6 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to trick a victim into performing actions they did not intend to do, which could be used to bypass security measures and gain unauthorized access. Exploitation of this issue requires user interaction, typically in the form of the victim clicking a link or visiting a malicious website.

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.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.4 2.4.4
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.5 2.4.5
Commerce Adobe 2.4.6 2.4.6
Commerce Adobe 2.4.6 2.4.6
Commerce Adobe 2.4.6 2.4.6
Commerce Adobe 2.4.6 2.4.6

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