Apache Wicket up to 8.0.0-M1 CSRF Prevention HTTP Header cross-site request forgery

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Apache Wicket up to 8.0.0-M1. The affected element is an unknown function of the component CSRF Prevention. The manipulation as part of HTTP Header leads to cross-site request forgery. This vulnerability is listed as CVE-2016-6806. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Apache Wicket up to 8.0.0-M1. It has been rated as problematic. This issue affects some unknown functionality of the component CSRF Prevention. The manipulation as part of a HTTP Header leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
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.
The bug was discovered 08/12/2016. The weakness was presented 10/03/2017 (Website). The advisory is shared at lists.apache.org. The identification of this vulnerability is CVE-2016-6806 since 08/12/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 416 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 6.25.0, 7.5.0 or 8.0.0-M2 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 100797
OpenVAS Name: Apache Wicket CSRF Detection Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Wicket 6.25.0/7.5.0/8.0.0-M2
Timeline
08/12/2016 🔍08/12/2016 🔍
10/02/2017 🔍
10/03/2017 🔍
10/03/2017 🔍
04/28/2020 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Status: Not defined
CVE: CVE-2016-6806 (🔍)
GCVE (CVE): GCVE-0-2016-6806
GCVE (VulDB): GCVE-100-107333
Entry
Created: 10/03/2017 10:49Updated: 04/28/2020 17:17
Changes: 10/03/2017 10:49 (64), 04/28/2020 17:17 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.