Jasperforge JasperReports Server Community Project 3.7.1 _flowExecutionKey cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jasperforge JasperReports Server Community Project 3.7.1. It has been rated as problematic. Impacted is an unknown function. Performing a manipulation of the argument _flowExecutionKey results in cross-site request forgery. This vulnerability is cataloged as CVE-2011-1911. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Jasperforge JasperReports Server Community Project 3.7.1 (Project Management Software). It has been classified as critical. This affects an unknown function. The manipulation of the argument _flowExecutionKey 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 confidentiality, integrity, and availability. The summary by CVE is:
JasperServer in JasperReports Server Community Project 3.7.0 and 3.7.1 uses a predictable _flowExecutionKey parameter, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via a brute-force approach.
The weakness was shared 09/20/2011 as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is uniquely identified as CVE-2011-1911 since 05/09/2011. 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. Technical details are known, but no exploit is available.
It is declared as highly functional.
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 databases at X-Force (69849) and SecurityFocus (BID 49649†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Highly functional
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
05/09/2011 🔍09/15/2011 🔍
09/20/2011 🔍
09/20/2011 🔍
03/23/2015 🔍
04/23/2025 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2011-1911 (🔍)
GCVE (CVE): GCVE-0-2011-1911
GCVE (VulDB): GCVE-100-58569
CERT: 🔍
X-Force: 69849 - JasperReports Server _flowExecutionKey parameter cross-site request forgery
SecurityFocus: 49649 - JasperReports Server '_flowExecutionKey' Parameter Cross Site Request Forgery Vulnerability
Entry
Created: 03/23/2015 16:50Updated: 04/23/2025 15:39
Changes: 03/23/2015 16:50 (50), 01/17/2018 12:11 (6), 12/01/2024 23:55 (17), 04/23/2025 15:39 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.