Security readout for executives and security teams
Plain-English summary
This Jira flaw lets someone without an account discover user information from affected Jira Server or Data Center systems. It is not described as allowing data modification or service disruption, but user enumeration can support phishing, credential attacks, and further targeting.
Executive priority
Treat this as a moderate-priority exposure reduction item. It does not indicate full compromise, but unauthenticated user discovery can materially improve attacker targeting and should be remediated during normal patch cycles, faster for internet-facing Jira.
Technical view
CVE-2020-36289 is an information disclosure issue tied to improper authorization in QueryComponentRendererValue!Default.jspa. CVSS 3.1 is 5.3: network reachable, low complexity, unauthenticated, no user interaction, low confidentiality impact, no integrity or availability impact.
Likely exposure
Organizations running Atlassian Jira Server or Jira Data Center before 8.5.13, 8.6.0 through before 8.13.5, or 8.14.0 through before 8.15.1 are potentially exposed, especially if Jira is reachable from the internet or broad internal networks.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation is remotely reachable and unauthenticated, making this useful for reconnaissance rather than direct compromise based on available evidence.
Researcher notes
The source bundle names the endpoint and affected version bands but does not provide detailed exploit mechanics, proof-of-concept status, or compensating controls. Analysis should remain bounded to authorization failure and user enumeration unless vendor material adds detail.
Mitigation direction
- Upgrade affected Jira Server or Data Center instances to 8.5.13, 8.13.5, 8.15.1, or later supported releases.
- Review Atlassian JRASERVER-71559 for version-specific vendor guidance before scheduling remediation.
- Restrict Jira access to trusted networks where business requirements allow.
- Monitor for unusual unauthenticated requests to the affected JSPA endpoint.
Validation and detection
- Inventory all Jira Server and Data Center deployments and record exact versions.
- Compare each instance against the affected version ranges in the CVE description.
- Confirm internet-facing Jira instances receive priority review.
- Check access logs for unauthenticated traffic to QueryComponentRendererValue!Default.jspa.
- Verify upgraded instances are outside the affected version ranges.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36289 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-71559CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.