Cryptographically weak CSRF tokens in Apache MyFaces
🔗 CVE IDs covered (1)
📋 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
🎯 Affected products4
- maven/org.apache.myfaces.core:myfaces-core-module:< 2.0.25
- maven/org.apache.myfaces.core:myfaces-core-module:>= 2.1.0, < 2.1.19
- maven/org.apache.myfaces.core:myfaces-core-module:>= 2.2.0, < 2.2.14
- maven/org.apache.myfaces.core:myfaces-core-module:>= 2.3.0, < 2.3.8
🔗 References (8)
- https://nvd.nist.gov/vuln/detail/CVE-2021-26296
- https://github.com/apache/myfaces/commit/cc6e1cc7b9aa17e52452f7f2657b3af9c421b2b2
- https://issues.apache.org/jira/browse/MYFACES-4373
- https://lists.apache.org/thread.html/r2b73e2356c6155e9ec78fdd8f72a4fac12f3e588014f5f535106ed9b%40%3Cannounce.apache.org%3E
- http://packetstormsecurity.com/files/161484/Apache-MyFaces-2.x-Cross-Site-Request-Forgery.html
- http://seclists.org/fulldisclosure/2021/Feb/66
- https://security.netapp.com/advisory/ntap-20210528-0007/
- https://github.com/advisories/GHSA-gq67-pp9w-43gp