LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41306: Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view private...

Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view private project and filter names via an Insecure Direct Object References (IDOR) vulnerability in the Average Time in Status Gadget. The affected versions are before version 8.13.12, and from version 8.14.0 before 8.20.0.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw could let an anonymous remote user see private Jira project and filter names through the Average Time in Status Gadget. It is a confidentiality issue: the sources do not indicate data modification, service disruption, or active exploitation.

Executive priority

Treat as high priority for exposed Jira environments because private project and filter names can reveal sensitive business activity. Prioritize internet-facing and anonymous-access instances, then internal instances with broad network reach.

Technical view

CVE-2021-41306 is an IDOR issue, CWE-639, in Atlassian Jira Server and Jira Data Center. Affected versions are before 8.13.12 and 8.14.0 through before 8.20.0. CVSS 3.1 is 7.5, driven by unauthenticated network access and high confidentiality impact.

Likely exposure

Organizations running Jira Server or Data Center in the affected version ranges are exposed, especially where Jira is reachable by anonymous users or from the internet. The disclosed impact is viewing private project and filter names, not full project content.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Exploitation is plausible because the vector is network-accessible, low complexity, unauthenticated, and requires no user interaction, but public weaponization is not established by the supplied evidence.

Researcher notes

The available sources identify the vulnerable component, weakness class, version ranges, and confidentiality impact, but provide limited implementation detail. Avoid assuming broader Jira data exposure unless confirmed by vendor documentation or controlled validation.

Mitigation direction

  • Upgrade Jira Server/Data Center to 8.13.12 or later in that line.
  • Upgrade 8.14.x-8.19.x deployments to 8.20.0 or later.
  • Check Atlassian JRASERVER-72915 for vendor-specific remediation guidance.
  • Reduce anonymous Jira exposure where business requirements allow.

Validation and detection

  • Inventory all Jira Server and Data Center instances and versions.
  • Flag versions before 8.13.12 as affected.
  • Flag versions from 8.14.0 before 8.20.0 as affected.
  • Confirm externally reachable Jira instances are prioritized first.
  • After remediation, verify the running Jira version is outside affected ranges.
Prepared
Confidence
high
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2021-41306 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-41306Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJira Serverunspecified, 8.14.0, unspecifiedListed
AtlassianJira Data Centerunspecified, 8.14.0, unspecifiedListed
Weakness

CWE details

CWE-639

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.