CVE-2021-26296GHSA-GQ67-PP9W-43GP
Cross-Site Request Forgery (CSRF) vulnerability in Apache MyFaces
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.14, 2.3.8, 2.3-next-M5, 3.0.0, 2.0.25, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache MyFaces Core
From Apache MyFaces Core 2.2 · fixed in 2.2.14; From Apache MyFaces Core 2.3 · fixed in 2.3.8; From Apache MyFaces Core 2.3-next · fixed in 2.3-next-M5; From Apache MyFaces Core 3.0 · fixed in 3.0.0
- org.apache.myfaces.core:myfaces-core-moduleMaven
fixed in 2.0.25
- org.apache.myfaces.core:myfaces-core-moduleMaven
From 2.1.0 · fixed in 2.1.19
- org.apache.myfaces.core:myfaces-core-moduleMaven
From 2.2.0 · fixed in 2.2.14
- org.apache.myfaces.core:myfaces-core-moduleMaven
From 2.3.0 · fixed in 2.3.8