LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20101: Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view whiteli...

Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view whitelist rules via a Broken Access Control vulnerability in the /rest/whitelist/<version>/check endpoint. The affected versions are before version 8.13.3, and from version 8.14.0 before 8.14.1.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw lets unauthenticated remote users view Jira whitelist rules. It does not directly change data or disrupt service, but it can expose trust relationships and integration details that help an attacker map the environment.

Executive priority

Treat as a medium-priority information exposure issue. It is not described as code execution or data modification, but exposed Jira metadata can support broader attack planning.

Technical view

CVE-2019-20101 is a broken access control issue in Atlassian Jira Server and Data Center. Affected versions expose whitelist rule information through the /rest/whitelist/<version>/check endpoint to anonymous remote attackers. The CVSS 3.1 score is 5.3, confidentiality-only impact.

Likely exposure

Organizations running Jira Server or Jira Data Center before 8.13.3, or 8.14.0 before 8.14.1, are potentially exposed. Risk is higher where Jira is internet-facing or reachable by untrusted users.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is network-accessible, low-complexity, requires no privileges or user interaction, and leaks limited information.

Researcher notes

Evidence is limited to the CVE description and Atlassian references. No CWE, exploit proof, or detailed advisory text is included in the provided bundle. Avoid assuming affected Cloud products or unrelated Jira versions.

Mitigation direction

  • Upgrade Jira Server and Data Center to 8.13.3, 8.14.1, or later supported versions.
  • Review Atlassian issue JRASERVER-72618 for vendor-specific remediation details.
  • Reduce untrusted network access to Jira while vulnerable versions remain in service.
  • Inventory and retire unsupported Jira Server deployments where applicable.

Validation and detection

  • Identify all Jira Server and Data Center instances and record exact versions.
  • Confirm no instance runs before 8.13.3 or 8.14.0 without 8.14.1.
  • Check whether Jira is reachable from the internet or untrusted networks.
  • Verify unauthenticated users cannot retrieve whitelist information from the documented endpoint.
  • Review access logs for anonymous requests to the whitelist check endpoint.
Prepared
Confidence
high
Sources
4

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.

cve · low confidence lookup

CVE-2019-20101 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2019-20101Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJira Serverunspecified, 8.14.0, unspecifiedListed
AtlassianJira Data Centerunspecified, 8.14.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.