LiveActive security incident?Get immediate response
CVE Record

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

Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view the names of private projects and filters via an Insecure Direct Object References (IDOR) vulnerability in the Average Number of Times in Status Gadget. The affected versions are before version 8.13.12..

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Jira flaw could let an unauthenticated remote person learn names of private projects and filters. That may expose sensitive business, customer, or security program context even without data modification. The supplied sources identify Jira Server and Data Center versions before 8.13.12 as affected.

Executive priority

Treat as high priority where Jira is exposed to the internet or contains sensitive project names. The issue leaks metadata, not full project content, but private names can reveal customers, incidents, internal initiatives, or security work.

Technical view

CVE-2021-41305 is a CWE-639 IDOR in Jira Server/Data Center's Average Number of Times in Status Gadget. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is most relevant for internet-accessible or broadly reachable Jira Server/Data Center deployments running versions before 8.13.12, especially where anonymous users can reach dashboard gadgets.

Exploitation context

The supplied bundle does not establish active exploitation. CISA KEV status is false, and the cited sources only describe the vulnerability and affected product/version boundary.

Researcher notes

Evidence is limited to the CVE record and Atlassian issue reference. The source bundle names the vulnerable gadget and fixed boundary before 8.13.12, but does not provide exploit telemetry or a broader version matrix.

Mitigation direction

  • Upgrade affected Jira Server/Data Center deployments to 8.13.12 or later per Atlassian guidance.
  • Confirm all externally reachable Jira instances are inventoried and version-checked.
  • Review anonymous access settings for Jira dashboards and gadgets.
  • If upgrade is delayed, consult Atlassian guidance for supported temporary mitigations.

Validation and detection

  • Identify Jira Server and Data Center instances and record exact versions.
  • Flag any deployment running before 8.13.12 as potentially affected.
  • Review whether anonymous users can reach dashboards or gadgets.
  • Check logs for unusual anonymous access to Jira gadget or dashboard resources.
Prepared
Confidence
high
Sources
3

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-41305 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-41305Attack 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 ServerunspecifiedListed
AtlassianJira Data CenterunspecifiedListed
Weakness

CWE details

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.