First published: Mon Oct 02 2017(Updated: )
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.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Wicket | =6.20.0 | |
Apache Wicket | =6.21.0 | |
Apache Wicket | =6.22.0 | |
Apache Wicket | =6.23.0 | |
Apache Wicket | =6.24.0 | |
Apache Wicket | =7.0.0 | |
Apache Wicket | =7.1.0 | |
Apache Wicket | =7.2.0 | |
Apache Wicket | =7.3.0 | |
Apache Wicket | =7.4.0 | |
Apache Wicket | =8.0.0-m1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6806 has a critical severity rating due to its impact on CSRF (Cross-Site Request Forgery) prevention measures.
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.
CVE-2016-6806 addresses a weakness in CSRF prevention that fails to adequately handle certain cross-origin requests.
CVE-2016-6806 affects Apache Wicket versions 6.x before 6.25.0, 7.x before 7.5.0, and 8.0.0-M1.
Failing to address CVE-2016-6806 can lead to vulnerabilities that may allow attackers to perform unauthorized actions on behalf of users.