VDB
Sign up
HIGH

GHSA-gq67-pp9w-43gp

Cryptographically weak CSRF tokens in Apache MyFaces

Quick fix

GHSA-gq67-pp9w-43gp — org.apache.myfaces.core:myfaces-core-module: upgrade to the fixed version with the command below.

# pom.xml: bump <version>2.0.25</version> for org.apache.myfaces.core:myfaces-core-module

Details

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

Are you affected?

Enter the version of the package you're using.

Affected packages

Maven/org.apache.myfaces.core:myfaces-core-module
Introduced in: 0Fixed in: 2.0.25
Fix# pom.xml: bump <version>2.0.25</version> for org.apache.myfaces.core:myfaces-core-module
Maven/org.apache.myfaces.core:myfaces-core-module
Introduced in: 2.1.0Fixed in: 2.1.19
Fix# pom.xml: bump <version>2.1.19</version> for org.apache.myfaces.core:myfaces-core-module
Maven/org.apache.myfaces.core:myfaces-core-module
Introduced in: 2.2.0Fixed in: 2.2.14
Fix# pom.xml: bump <version>2.2.14</version> for org.apache.myfaces.core:myfaces-core-module
Maven/org.apache.myfaces.core:myfaces-core-module
Introduced in: 2.3.0Fixed in: 2.3.8
Fix# pom.xml: bump <version>2.3.8</version> for org.apache.myfaces.core:myfaces-core-module

References