Data CenterApplication · Atlassian
CVE-2020-36237
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 unauthenticated remote attackers to view custom field options via an Information Disclosure vulnerability in the /rest/api/2/customFieldOption/ endpoint. The affected versions are before version 8.15.0.
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 where the /rest/api/2/customFieldOption/ endpoint allows unauthenticated remote attackers to view custom field options. The endpoint does not properly enforce authentication, exposing potentially sensitive configuration data about custom fields in the Jira system.
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
< 8.15.0
JiraApplication
< 8.15.0CVSS 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.
-
Check installed Jira versionLog into the Jira Administration console and navigate to 'Applications' > 'Jira software' or use the /about2 page to view the version number. Alternatively, check the installation directory for a version file or run 'java -jar atlassian-jira-software -v' if you have CLI access.Affected if The installed version is below 8.15.0 (e.g., 8.14.x, 8.13.x, 8.0.x, 7.x, etc.)
-
Verify custom fields are configuredNavigate to 'Issues' > 'Custom Fields' in the Jira Administration console, or query the database for entries in the 'CustomField' table if you have database access.Affected if Any custom fields exist in the Jira instance - the vulnerability exposes options for configured custom fields even without authentication.
-
Test endpoint authentication enforcementSend an unauthenticated HTTP GET request to https://your-jira-base-url/rest/api/2/customFieldOption/{id} using curl or a browser. Replace {id} with a known custom field option ID (e.g., 1, 10000) or attempt to enumerate options.Affected if The endpoint returns JSON data containing custom field option details without requiring any authentication (HTTP 200 response with custom field data instead of HTTP 401/403).
The environment is affected if Jira Server or Data Center version is below 8.15.0 AND the /rest/api/2/customFieldOption/ endpoint is accessible without authentication, exposing custom field configuration data.
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.15.0
Upgrade Atlassian Jira Server and Data Center to version 8.15.0 or later to patch the vulnerability. As a temporary measure, network-level access controls can be applied to restrict access to the affected endpoint.
Fix this in Data Center
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36237 — 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-36237 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