LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20419: Affected versions of Atlassian Jira Server and Data Center allow remote attackers to execute arbitrary code...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects Atlassian Jira Server and Data Center. A remote attacker could execute arbitrary code through a Tomcat DLL hijacking issue in vulnerable Jira versions. No CVSS score or active exploitation evidence is provided in the source bundle, but remote code execution on Jira can create serious business risk.

Executive priority

Prioritize this as a high-impact remediation item if affected Jira versions are present. The available sources do not confirm exploitation, but remote code execution in Jira can affect sensitive workflows, credentials, integrations, and operational continuity.

Technical view

Affected Jira Server and Data Center versions are before 8.5.5, and 8.6.0 before 8.7.2. The vulnerability is described as remote arbitrary code execution via DLL hijacking in Tomcat. The bundle provides no CWE, CVSS vector, exploit details, or environment prerequisites.

Likely exposure

Organizations running Jira Server or Data Center in the affected version ranges may be exposed, especially where Jira is reachable by untrusted networks. The bundle only explicitly lists Atlassian Jira Server in the affected object, while the title and description also name Data Center.

Exploitation context

The source bundle does not state active exploitation, and KEV is false. Treat exploitation status as unconfirmed. The technical impact is serious because successful exploitation is described as arbitrary code execution, but no public exploit path is included in the provided sources.

Researcher notes

Evidence is limited to CVE and Atlassian issue references. The bundle lacks CVSS, CWE, exploit prerequisites, and detailed patch notes. Avoid assuming exploitability beyond the stated remote code execution via Tomcat DLL hijacking description.

Mitigation direction

  • Inventory Jira Server and Data Center versions across all environments.
  • Upgrade affected Jira versions to 8.5.5, 8.7.2, or later vendor-supported releases.
  • Review Atlassian JRASERVER-70945 for any current vendor guidance.
  • Prioritize remediation for externally reachable or high-trust Jira instances.

Validation and detection

  • Confirm whether each Jira instance is before 8.5.5 or 8.6.0 before 8.7.2.
  • Document whether Jira Server or Data Center is deployed.
  • Check exposure paths from the internet and untrusted internal networks.
  • Verify the installed version after upgrade or remediation.
  • Record evidence from asset inventory and Jira administration screens.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-20419 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJira Serverunspecified, 8.6.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.