| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Grails Console up to 1.5.10/2.0.7 and classified as problematic. This issue affects some unknown processing. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2016-6521. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Grails Console up to 1.5.10/2.0.7. It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:
Cross-site request forgery (CSRF) vulnerability in Grails console (aka Grails Debug Console and Grails Web Console) 2.0.7, 1.5.10, and earlier allows remote attackers to hijack the authentication of users for requests that execute arbitrary Groovy code via unspecified vectors.
The bug was discovered 07/01/2016. The weakness was disclosed 01/23/2017 (Website). It is possible to read the advisory at openwall.com. This vulnerability is uniquely identified as CVE-2016-6521 since 08/02/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 206 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92267†). Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/01/2016 🔍08/01/2016 🔍
08/02/2016 🔍
01/23/2017 🔍
01/23/2017 🔍
01/24/2017 🔍
05/14/2026 🔍
Sources
Advisory: 54Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-6521 (🔍)
GCVE (CVE): GCVE-0-2016-6521
GCVE (VulDB): GCVE-100-95847
SecurityFocus: 92267 - grails-console CVE-2016-6521 Cross Site Request Forgery Vulnerability
OSVDB: - CVE-2016-6521 - Grails - Cross-Site Request Forgery Issue
Entry
Created: 01/24/2017 08:32Updated: 05/14/2026 15:34
Changes: 01/24/2017 08:32 (56), 07/30/2020 16:46 (6), 11/03/2022 09:34 (2), 05/14/2026 15:34 (17)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.