LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41312: Affected versions of Atlassian Jira Server and Data Center allow a remote attacker who has had their access...

Affected versions of Atlassian Jira Server and Data Center allow a remote attacker who has had their access revoked from Jira Service Management to enable and disable Issue Collectors on Jira Service Management projects via an Improper Authentication vulnerability in the /secure/ViewCollectors endpoint. The affected versions are before version 8.19.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-41312 is an Atlassian Jira Server and Data Center authentication flaw. A remote attacker whose Jira Service Management access was revoked could still enable or disable Issue Collectors on Jira Service Management projects, affecting project intake and integrity. Sources identify affected versions as before 8.19.1.

Executive priority

Treat this as a high-priority integrity issue for self-managed Jira environments. Prioritize upgrades where Jira Service Management supports customer intake or operational workflows.

Technical view

The issue is CWE-287 Improper Authentication in Jira's /secure/ViewCollectors endpoint. The CVSS 3.1 score is 7.5 with network access, low complexity, no privileges, no user interaction, and high integrity impact. No confidentiality or availability impact is claimed in the provided CVE data.

Likely exposure

Organizations running Atlassian Jira Server or Jira Data Center versions earlier than 8.19.1 are potentially exposed, especially where Jira Service Management projects use Issue Collectors.

Exploitation context

The provided bundle does not show CISA KEV listing or source-backed active exploitation. The described attacker is remote and previously had Jira Service Management access revoked.

Researcher notes

Focus validation on Jira Server/Data Center before 8.19.1 and the /secure/ViewCollectors authorization path. Evidence supports integrity impact, but not data disclosure, service outage, or active exploitation.

Mitigation direction

  • Upgrade Jira Server or Data Center to version 8.19.1 or later.
  • Review Atlassian advisory JRASERVER-72801 for exact affected and fixed versions.
  • Audit Jira Service Management Issue Collector settings for unauthorized changes.
  • Restrict external access to Jira administrative and project configuration surfaces where feasible.

Validation and detection

  • Inventory Jira Server and Data Center versions and identify instances below 8.19.1.
  • Check whether Jira Service Management projects use Issue Collectors.
  • Review change history or administrative logs for unexpected collector enablement or disablement.
  • Confirm revoked users no longer have effective access to Jira Service Management project controls.
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 · 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-41312 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:N/I:H/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:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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