~ / search / GHSA-gq67-pp9w-43gp

GHSA-gq67-pp9w-43gp

Cryptographically weak CSRF tokens in Apache MyFaces

Source: GitHub Advisory Database (reviewed) High CVE-2021-26296

Packages

EcosystemPackageAffectedFixed in
Maven org.apache.myfaces.core:myfaces-core-module < 2.0.25 2.0.25
Maven org.apache.myfaces.core:myfaces-core-module >= 2.1.0, < 2.1.19 2.1.19
Maven org.apache.myfaces.core:myfaces-core-module >= 2.2.0, < 2.2.14 2.2.14
Maven org.apache.myfaces.core:myfaces-core-module >= 2.3.0, < 2.3.8 2.3.8

Details

As written in the advisory (Markdown source, shown as plain text).

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. Mitigation: 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

References

External links from the advisory. They lead to third-party sites.