dbcve.org
Data CenterApplication · Atlassian

CVE-2019-20101

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-14
Fix available
A fix is available. Upgrade to 8.13.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Broken Access Control vulnerability in Atlassian Jira Server and Data Center affecting the /rest/whitelist/<version>/check endpoint. Anonymous remote attackers can view whitelist rules without authentication. Affected versions are before 8.13.3, and from 8.14.0 before 8.14.1.

MitigationUpgrade Jira Server or Data Center to version 8.13.3, 8.14.1, or later to patch the broken access control vulnerability in the whitelist endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Data CenterApplication
Affected:< 8.13.3= 8
JiraApplication
Affected:< 8.13.3= 8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Jira version
    Navigate to Jira Administration > System > Troubleshooting and support tools > System Info, or check the 'atlassian-jira/WEB-INF/built.xml' file for the version number.
    Affected if The installed version is before 8.13.3, or is 8.14.0.
  2. Verify whitelist feature is enabled
    Navigate to Jira Administration > Apps > Whitelist (or /admin/whitelist.action), or check the 'whitelist' table in the Jira database for entries.
    Affected if Whitelist rules are configured or the whitelist feature is active.
  3. Test vulnerable endpoint access
    Send a GET request to /rest/whitelist/1/check without any authentication headers, using curl or a browser.
    Affected if The endpoint returns whitelist rules or configuration data without requiring login credentials.
  4. Confirm authentication is bypassed
    Attempt to access /rest/whitelist/1/check from an incognito browser window or using a tool like curl without providing cookies or authentication tokens.
    Affected if HTTP response returns 200 OK with whitelist content instead of redirecting to login.

You are affected if your Jira version is below 8.13.3 or is exactly 8.14.0, and the whitelist endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.13.3 or later
Fixed in 8.13.3
Interim mitigation

Upgrade Jira Server or Data Center to version 8.13.3, 8.14.1, or later to patch the broken access control vulnerability in the whitelist endpoint.

Recommended fix High confidence

8.13.3 (for 8.13.x line) or 8.14.1+/8.20.x LTS (for 8.14.x line)

  1. 1. Identify current Jira version by navigating to Jira Administration > System > System Info
  2. 2. For Jira 8.13.x versions: plan upgrade to version 8.13.3
  3. 3. For Jira 8.14.0: plan upgrade to version 8.14.1 or later (recommended: latest 8.14.x LTS or 8.20.x)
  4. 4. Perform full backup of Jira database and home directory before upgrade
  5. 5. Test upgrade in non-production/staging environment first
  6. 6. Schedule maintenance window and stop Jira
  7. 7. Run Jira upgrade installer for chosen fixed version
  8. 8. Start Jira and verify the /rest/whitelist endpoint no longer allows anonymous access
Caveat Major version upgrades may have plugin/app compatibility issues; review Atlassian Marketplace for app compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-20101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-20101 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data