Atlassian JIRA Server/Data Center up to 8.5.x JMX Monitoring cross site request forgery
| CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|
Current Exploit Price (β)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
|
|---|---|---|
|
5.1 |
$0-$5k | 3.31+ |
A vulnerability was found in Atlassian JIRA Server and Data Center up to 8.5.x (Bug Tracking Software). It has been rated as problematic. Affected by this issue is some unknown processing of the component JMX Monitoring. The manipulation with an unknown input leads to a cross site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. Impacted is integrity. An attacker might be able force legitimate users to initiate unwanted actions within the web application.
The weakness was published 02/06/2020. This vulnerability is handled as CVE-2019-20405 since 01/23/2020. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 8.6.0 eliminates this vulnerability.
Similar entries are available at 149749, 149748 and 149747.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: π
Exploiting
Class: Cross site request forgery (CWE-352)
Local: No
Remote: Yes
Availability: π
Status: Not defined
Price Prediction: π
Current Price Estimation: π
| 0-Day | unlock | unlock | unlock | unlock |
|---|---|---|---|---|
| Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Threat: π
Adversaries: π
Geopolitics: π
Economy: π
Predictions: π
Remediation: π
Countermeasures
Recommended: Upgrade
Status: π
0-Day Time: π
Upgrade: JIRA Server/Data Center 8.6.0
Timeline
01/23/2020 CVE assigned
02/06/2020 Advisory disclosed
02/06/2020 VulDB entry created
02/06/2020 VulDB last update
Sources
Vendor: atlassian.com
CVE: CVE-2019-20405 (π)
See also: π
Entry
Created: 02/06/2020 01:17 PM
Complete: π
Comments
Interested in the pricing of exploits?
See the underground prices here!
Comments are closed.
No comments yet. Please log in to comment.