Apache Wicket vulnerable to CSRF attacks
Apache Software Foundation Apache Wicket
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.wicket:wicket-core Maven |
|
|
Apache Software Foundation Apache Wicket
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.wicket:wicket-core Maven |
|
|
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.
From the CVE record · apache
Apache Wicket’s CSRF prevention can miss cross-origin requests when the Origin header is absent, and some server-side targets were not checked at all. An attacker can bypass the CSRF check in those cases; the input does not specify authentication requirements or user interaction.
Check applications using Maven org.apache.wicket:wicket-core versions 6.20.0 through before 6.25.0, 7.0.0 through before 7.5.0, or 8.0.0-M1.