CVE Vulnerabilities

CVE-2024-26273

Cross-Site Request Forgery (CSRF)

Published: Oct 22, 2024 | Modified: Oct 30, 2024
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Cross-site request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.4.0 through 7.4.3.103, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, 2023.Q3.1 through 2023.Q3.5, 7.4 GA through update 92 and 7.3 update 29 through update 35 allows remote attackers to (1) change user passwords, (2) shut down the server, (3) execute arbitrary code in the scripting console, (4) and perform other administrative actions via the _com_liferay_commerce_catalog_web_internal_portlet_CommerceCatalogsPortlet_redirect parameter.

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
Digital_experience_platform Liferay 7.3-update29 (including) 7.3-update29 (including)
Digital_experience_platform Liferay 7.3-update32 (including) 7.3-update32 (including)
Digital_experience_platform Liferay 7.3-update33 (including) 7.3-update33 (including)
Digital_experience_platform Liferay 7.3-update34 (including) 7.3-update34 (including)
Digital_experience_platform Liferay 7.3-update35 (including) 7.3-update35 (including)
Digital_experience_platform Liferay 7.4 (including) 7.4 (including)
Digital_experience_platform Liferay 2023-q3.1 (including) 2023-q3.1 (including)
Digital_experience_platform Liferay 2023-q3.5 (including) 2023-q3.5 (including)
Digital_experience_platform Liferay 2023-q4.0 (including) 2023-q4.0 (including)
Digital_experience_platform Liferay 2023-q4.2 (including) 2023-q4.2 (including)
Liferay_portal Liferay 7.4.0 (including) 7.4.3.104 (excluding)

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