Cross-Site Request Forgery (CSRF) vulnerability in Apache MyFaces
Apache Software Foundation Apache MyFaces Core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.myfaces.core:myfaces-core-module Maven |
|
|
Apache Software Foundation Apache MyFaces Core
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.myfaces.core:myfaces-core-module Maven |
|
|
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.
From the CVE record · apache
In its default configuration, affected Apache MyFaces Core versions use cryptographically weak CSRF tokens. An attacker may be able to calculate a future token and trick a user into performing unwanted actions in an application; the input does not specify whether attacker authentication is needed.
Check applications running Apache MyFaces Core, including Maven package org.apache.myfaces.core:myfaces-core-module in the listed affected ranges, as well as the affected prerelease versions named in the description.