JiraApplication · Atlassian
CVE-2020-14185
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 Jira Server allow remote unauthenticated attackers to enumerate issue keys via a missing permissions check in the ActionsAndOperations resource. The affected versions are before 7.13.18, from version 8.0.0 before 8.5.9, and from version 8.6.0 before version 8.12.2.
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 confidenceAffected Jira Server versions contain a missing permissions check in the ActionsAndOperations resource that allows remote unauthenticated attackers to enumerate valid issue keys. This information disclosure could aid attackers in targeting specific issues or planning further attacks.
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
JiraApplication
< 7.13.18
Jira ServerApplication
>= 8.0.0, < 8.5.9>= 8.6.0, < 8.12.2CVSS 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.
-
Determine Jira Server versionLog in as administrator and navigate to Administration > System > Troubleshooting and support tools > System info, or access /secure/AdminHello.jspa endpoint. The version is displayed on the page.Affected if Version is below 7.13.18, or between 8.0.0 and 8.5.9 inclusive, or between 8.6.0 and 8.12.2 inclusive
-
Verify ActionsAndOperations endpoint accessibilitySend a GET request to /rest/api/2/actionsandoperations without providing authentication credentials. Use curl or a browser: curl -s -o /dev/null -w "%{http_code}" https://your-jira-host/rest/api/2/actionsandoperationsAffected if HTTP response returns 200 OK with JSON content instead of 401 Unauthorized or 403 Forbidden - this indicates the endpoint is accessible without authentication and the vulnerability is present
-
Confirm issue key enumeration worksSend a GET request to /rest/api/2/actionsandoperations?issueKey=YOUR-EXISTING-PROJECT-KEY without authentication. If the response contains valid project or issue information, the enumeration is successful.Affected if Response contains project or issue details (such as available actions, operations, or project identifiers) without authentication
User is affected if Jira Server version falls within the vulnerable ranges AND the /rest/api/2/actionsandoperations endpoint is accessible to unauthenticated users, allowing enumeration of valid issue keys.
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 data7.13.188.5.98.12.2
Upgrade Jira Server to version 7.13.18, 8.5.9, 8.12.2 or later to patch the missing authorization check in the ActionsAndOperations resource.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14185 — 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-14185 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