GHSA-gq67-pp9w-43gp

Cryptographically weak CSRF tokens in Apache MyFaces

En bref

Publiée
Mise à jour
CVE
CVE-2021-26296

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

Paquets affectés

PaquetVersions
Maven · org.apache.myfaces.core:myfaces-core-moduleintroduced 0, fixed 2.0.25
Maven · org.apache.myfaces.core:myfaces-core-moduleintroduced 2.1.0, fixed 2.1.19
Maven · org.apache.myfaces.core:myfaces-core-moduleintroduced 2.2.0, fixed 2.2.14
Maven · org.apache.myfaces.core:myfaces-core-moduleintroduced 2.3.0, fixed 2.3.8

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database