CVE-2021-26296

Cross-Site Request Forgery (CSRF) vulnerability in Apache MyFaces

Published Feb 19, 2021 CVSS 3.1 · 7.5 High EPSS 2.9% KEV · Not listed
Description
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.

Analysis

No analysis available yet

Remediation

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2021-1329 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.
Github GHSA Github GHSA GHSA-gq67-pp9w-43gp Cryptographically weak CSRF tokens in Apache MyFaces
History

No history.

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Feb 13, 2025, 4:27 PM
Reserved
Jan 28, 2021, 12:00 AM
Status
Modified
Published
Feb 19, 2021, 9:15 AM
Modified
Jun 17, 2026, 3:43 AM
Severity
Moderate
Public date
Feb 18, 2021, 12:00 AM