CVE-2016-6806: CSRF
Apache Wicket 6.x before 6.25.0, 7.x before 7.5.0, and 8.0.0-M1 provide a CSRF prevention measure that fails to discover some cross origin requests. The mitigation is to not only check the Origin HTTP header, but also take the Referer HTTP header into account when no Origin was provided. Furthermore, not all Wicket server side targets were subjected to the CSRF check. This was also fixed.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-6806?
CVE-2016-6806 has a critical severity rating due to its impact on CSRF (Cross-Site Request Forgery) prevention measures.
How do I fix CVE-2016-6806?
To fix CVE-2016-6806, update to Apache Wicket version 6.25.0 or later for the 6.x series, 7.5.0 or later for the 7.x series, or any stable release after 8.0.0-M1.
What vulnerability does CVE-2016-6806 address?
CVE-2016-6806 addresses a weakness in CSRF prevention that fails to adequately handle certain cross-origin requests.
Which versions of Apache Wicket are affected by CVE-2016-6806?
CVE-2016-6806 affects Apache Wicket versions 6.x before 6.25.0, 7.x before 7.5.0, and 8.0.0-M1.
What are the implications of not addressing CVE-2016-6806?
Failing to address CVE-2016-6806 can lead to vulnerabilities that may allow attackers to perform unauthorized actions on behalf of users.