CVE-2019-20405: CSRF
First published: Tue Feb 04 2020(Updated: )
The JMX monitoring flag in Atlassian Jira Server and Data Center before version 8.6.0 allows remote attackers to turn the JMX monitoring flag off or on via a Cross-site request forgery (CSRF) vulnerability.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Data Center | >=7.13.0<8.6.0 | |
| Atlassian Server | >=7.13.0<8.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-20405?
CVE-2019-20405 is considered a medium severity vulnerability due to its potential for CSRF exploitation.
How do I fix CVE-2019-20405?
To fix CVE-2019-20405, upgrade to Atlassian Jira Server and Data Center version 8.6.0 or higher.
What types of software are affected by CVE-2019-20405?
CVE-2019-20405 affects Atlassian Jira Server and Data Center versions between 7.13.0 and 8.6.0.
Can CVE-2019-20405 be exploited remotely?
Yes, CVE-2019-20405 can be exploited remotely by attackers through a CSRF attack.
What does CVE-2019-20405 allow an attacker to do?
CVE-2019-20405 allows attackers to toggle the JMX monitoring flag on or off, potentially compromising system performance.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/severity
- agent/weakness
- agent/first-publish-date
- agent/event
- agent/description
- agent/author
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian data center
- version/atlassian data center/7.13.0
- canonical/atlassian server
- version/atlassian server/7.13.0