CVE-2019-20419
First published: Fri Jul 03 2020(Updated: )
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to execute arbitrary code via a DLL hijacking vulnerability in Tomcat. The affected versions are before version 8.5.5, and from version 8.6.0 before 8.7.2.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Data Center | <8.5.5 | |
| Atlassian Data Center | >=8.6.0<8.7.2 | |
| Atlassian Server | <8.5.5 | |
| Atlassian Server | >=8.6.0<8.7.2 |
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-20419?
CVE-2019-20419 has a critical severity level due to the potential for remote code execution.
How do I fix CVE-2019-20419?
To mitigate CVE-2019-20419, upgrade to version 8.5.5 or later, or between 8.6.0 and 8.7.2 for Atlassian Jira Server and Data Center.
Which versions of Atlassian Jira are affected by CVE-2019-20419?
CVE-2019-20419 affects Atlassian Jira Server and Data Center versions prior to 8.5.5 and versions from 8.6.0 up to, but not including, 8.7.2.
What type of vulnerability is CVE-2019-20419?
CVE-2019-20419 is a DLL hijacking vulnerability that allows remote attackers to execute arbitrary code.
Is there a workaround for CVE-2019-20419?
There is no documented workaround for CVE-2019-20419; upgrading to the patched versions is recommended.
- agent/type
- agent/softwarecombine
- agent/references
- agent/severity
- agent/weakness
- agent/description
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian data center
- version/atlassian data center/8.6.0
- canonical/atlassian server
- version/atlassian server/8.6.0