Jira Data CenterApplication · Atlassian
CVE-2020-14179
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 · uneditedAffected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA names via an Information Disclosure vulnerability in the /secure/QueryComponent!Default.jspa endpoint. The affected versions are before version 8.5.8, and from version 8.6.0 before 8.11.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 confidenceThis is an information disclosure vulnerability in Atlassian Jira Server and Data Center. The /secure/QueryComponent!Default.jspa endpoint allows remote, unauthenticated attackers to view custom field names and custom SLA names. Affected versions are before 8.5.8 and from 8.6.0 before 8.11.1.
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
Jira Data CenterApplication
< 8.5.8>= 8.6.0, < 8.11.1
Jira ServerApplication
< 8.5.8>= 8.6.0, < 8.11.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Jira version numberLog into Jira as an administrator and navigate to Administration > System > System Info, or access /secure/AdminHome.jspa and look for the 'Jira version' field in the system information sectionAffected if Version is below 8.5.8, or between 8.6.0 and 8.11.0 inclusive
-
Compare installed version to CVE rangeIf the version cannot be found in the UI, check the installation directory for a version file, or query the REST API endpoint /rest/api/2/serverInfo to retrieve the build number and versionAffected if Version falls outside the safe range of 8.5.8 or higher, or 8.11.1 or higher
-
Verify endpoint accessibilityFrom a browser or curl command, attempt to access http(s)://<jira-host>/secure/QueryComponent!Default.jspa without authenticationAffected if The endpoint loads and displays any content to an unauthenticated user (this confirms the vulnerability is exploitable in your environment)
You are affected if your Jira Server or Data Center version is between 8.5.0 and 8.11.0 (inclusive) and the QueryComponent endpoint is accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data8.5.88.11.1
Upgrade Jira Server or Data Center to version 8.5.8, 8.11.1, or later to patch the information disclosure vulnerability in the QueryComponent endpoint.
Fix this in Jira Data Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14179 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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