Security readout for executives and security teams
Plain-English summary
CVE-2020-4028 is an information disclosure issue in Jira Server and Data Center before 8.9.1. Unauthenticated users could sometimes tell whether certain Jira resources existed because Jira returned 404 responses instead of redirecting to login. The sources do not describe data theft, code execution, or privilege escalation.
Executive priority
Treat this as a lower-urgency information disclosure issue unless Jira is externally exposed or contains sensitive project metadata. Prioritize confirming versions and upgrading older Jira Server/Data Center deployments during normal vulnerability remediation cycles.
Technical view
Various Jira resources returned 404 to unauthenticated requests instead of consistently redirecting to the login page. That behavior could let unauthorized attackers infer resource existence. The bundle identifies Atlassian Jira Server and Data Center versions before 8.9.1 as affected, but provides no CVSS vector or CWE classification.
Likely exposure
Exposure is most relevant for Jira Server or Data Center instances running versions before 8.9.1, especially if reachable by untrusted users or the internet. The bundle does not identify affected resource types in detail.
Exploitation context
No active exploitation is stated in the source bundle, and the CVE is not listed as KEV. The described impact is unauthenticated resource-existence inference, useful for reconnaissance rather than direct compromise based on the available evidence.
Researcher notes
The public bundle is sparse: no CVSS, CWE, exploit details, or detailed resource list are provided. Analysis should remain limited to unauthenticated existence disclosure in Jira Server/Data Center before 8.9.1, as described by the CVE and Atlassian reference.
Mitigation direction
- Identify Jira Server and Data Center instances running before 8.9.1.
- Review Atlassian JRASERVER-71175 for vendor guidance and fixed-version details.
- Upgrade affected Jira deployments to 8.9.1 or later where applicable.
- Restrict unauthenticated access to Jira from untrusted networks where business operations allow.
Validation and detection
- Inventory Jira Server and Data Center versions across production and non-production environments.
- Confirm internet-facing Jira instances are not running versions before 8.9.1.
- Check unauthenticated access patterns for unexpected 404 responses on protected resources.
- Document whether compensating access controls limit untrusted unauthenticated requests.
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.
CVE-2020-4028 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-71175CVE 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.