JIRA up to 7.13.5/8.2.2/8.3.1 AddResolution.jspa cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JIRA up to 7.13.5/8.2.2/8.3.1. It has been classified as problematic. This issue affects some unknown processing of the file AddResolution.jspa. The manipulation leads to cross-site request forgery. This vulnerability is referenced as CVE-2019-11586. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in JIRA up to 7.13.5/8.2.2/8.3.1. It has been rated as problematic. This issue affects an unknown code block of the file AddResolution.jspa. The manipulation with an unknown input 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:
The AddResolution.jspa resource in Jira before version 7.13.6, from version 8.0.0 before version 8.2.3, and from version 8.3.0 before version 8.3.2 allows remote attackers to create new resolutions via a Cross-site request forgery (CSRF) vulnerability.
The weakness was published 08/23/2019. The identification of this vulnerability is CVE-2019-11586 since 04/29/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading to version 7.13.6, 8.2.3 or 8.3.2 eliminates this vulnerability.
Similar entries are available at VDB-140708, VDB-140707, VDB-140706 and VDB-140704. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JIRA 7.13.6/8.2.3/8.3.2
Timeline
04/29/2019 🔍08/23/2019 🔍
08/24/2019 🔍
12/01/2023 🔍
Sources
Advisory: jira.atlassian.comStatus: Not defined
CVE: CVE-2019-11586 (🔍)
GCVE (CVE): GCVE-0-2019-11586
GCVE (VulDB): GCVE-100-140705
See also: 🔍
Entry
Created: 08/24/2019 10:46Updated: 12/01/2023 14:02
Changes: 08/24/2019 10:46 (37), 08/04/2020 12:21 (17), 12/01/2023 14:02 (4)
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.