In the default configuration, Apache MyFaces Core versions 2.2.0 to 2.2.13, 2.3.0 to 2.3.7, 2.3-next-M1 to 2.3-next-M4, and 3.0.0-RC1 use cryptographically weak implicit and explicit cross-site request forgery (CSRF) tokens. Due to that limitation, it is possible (although difficult) for an attacker to calculate a future CSRF token value and to use that value to trick a user into executing unwanted actions on an application.
Fixes

Solution

No solution given by the vendor.


Workaround

Existing web.xml configuration parameters can be used to direct MyFaces to use SecureRandom for CSRF token generation: org.apache.myfaces.RANDOM_KEY_IN_VIEW_STATE_SESSION_TOKEN=secureRandom org.apache.myfaces.RANDOM_KEY_IN_CSRF_SESSION_TOKEN=secureRandom org.apache.myfaces.RANDOM_KEY_IN_WEBSOCKET_SESSION_TOKEN=secureRandom

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2025-02-13T16:27:52.470Z

Reserved: 2021-01-28T00:00:00.000Z

Link: CVE-2021-26296

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2021-02-19T09:15:13.283

Modified: 2024-11-21T05:56:02.610

Link: CVE-2021-26296

cve-icon Redhat

Severity : Moderate

Publid Date: 2021-02-18T00:00:00Z

Links: CVE-2021-26296 - Bugzilla

cve-icon OpenCVE Enrichment

No data.