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.
References
Link | Resource |
---|---|
https://lists.apache.org/thread.html/r2b73e2356c6155e9ec78fdd8f72a4fac12f3e588014f5f535106ed9b%40%3Cannounce.apache.org%3E | Mailing List Vendor Advisory |
http://seclists.org/fulldisclosure/2021/Feb/66 | Mailing List Third Party Advisory |
http://packetstormsecurity.com/files/161484/Apache-MyFaces-2.x-Cross-Site-Request-Forgery.html | Exploit Third Party Advisory VDB Entry |
https://security.netapp.com/advisory/ntap-20210528-0007/ | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2021-02-19 01:15
Updated : 2021-06-02 08:15
NVD link : CVE-2021-26296
Mitre link : CVE-2021-26296
JSON object : View
CWE
CWE-352
Cross-Site Request Forgery (CSRF)
Products Affected
apache
- myfaces
netapp
- oncommand_insight