CVE-2016-6806 Apache Wicket vulnerable to CSRF attacks

High 8.8 Published Updated

Apache Wicket's CSRF protection failed to check Referer headers and some server-side targets, allowing attackers to bypass CSRF defenses.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2016-6806?

CVE-2016-6806 is a high-severity vulnerability in Apache Wicket, published on 2 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-352

Which versions are affected by CVE-2016-6806?

6 open source packages ship an affected version, including org.apache.wicket:wicket-core. It affects 1 product.

PackageAffectedFixed in
org.apache.wicket:wicket-core MavenFrom 6.20.06.25.0
org.apache.wicket:wicket-core MavenFrom 6.20.06.25.0
org.apache.wicket:wicket-core MavenFrom 7.0.07.5.0
org.apache.wicket:wicket-core MavenFrom 7.0.07.5.0
org.apache.wicket:wicket-core MavenFrom 8.0.0-M18.0.0-M2
org.apache.wicket:wicket-core MavenFrom 8.0.0-M18.0.0-M2

Products include Apache Wicket.

How do I fix CVE-2016-6806?

Upgrade org.apache.wicket:wicket-core to a fixed version for your release line: 6.25.0, 7.5.0 or 8.0.0-M2.

Is CVE-2016-6806 being exploited?

There is no known exploitation of CVE-2016-6806 in the wild and no public exploit code.

Sources

Also known as GHSA-xc66-mg8r-q6r5.

Is CVE-2016-6806 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free