LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41309: Affected versions of Atlassian Jira Server and Data Center allow a user who has had their Jira Service Mana...

Affected versions of Atlassian Jira Server and Data Center allow a user who has had their Jira Service Management access revoked to export audit logs of another user's Jira Service Management project via a Broken Authentication vulnerability in the /plugins/servlet/audit/resource endpoint. The affected versions of Jira Server and Data Center are before version 8.19.1.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-41309 is an Atlassian Jira Server and Data Center authentication flaw. A user whose Jira Service Management access was revoked could still export audit logs for another user's Jira Service Management project, exposing limited audit information.

Executive priority

Schedule remediation through normal vulnerability management. Prioritize externally reachable Jira deployments and projects with sensitive audit history, but current sources support moderate urgency rather than crisis handling.

Technical view

Affected Jira Server and Data Center versions before 8.19.1 contain a broken authentication issue in /plugins/servlet/audit/resource. The CVSS 3.1 score is 5.3, with network access, low complexity, no user interaction, and low confidentiality impact.

Likely exposure

Exposure is most relevant for Jira Server or Jira Data Center deployments running versions before 8.19.1, especially where Jira is reachable over a network and Jira Service Management project audit logs exist.

Exploitation context

The source bundle does not identify active exploitation, and the CVE is not listed as KEV. Treat this as a confidentiality issue requiring version review and remediation, not an emergency zero-day based on the provided evidence.

Researcher notes

Evidence is limited to the CVE description and Atlassian issue reference. The affected endpoint and version boundary are stated, but the supplied sources do not provide exploit details, public exploitation evidence, or broader product impact.

Mitigation direction

  • Upgrade affected Jira Server or Data Center instances to 8.19.1 or later.
  • Review Atlassian JRASERVER-72803 for vendor-specific remediation guidance.
  • Restrict Jira access to trusted networks where operationally feasible.
  • Review revoked Jira Service Management access for sensitive projects.

Validation and detection

  • Inventory Jira Server and Data Center versions across managed environments.
  • Flag any instance running a version before 8.19.1.
  • Confirm Jira Service Management audit log exports follow current access decisions.
  • Review audit and access logs for unexpected audit export activity.
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 · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-41309 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
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

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-41309Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-287

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

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs