NVD / CVE Program· CNA atlassian

CVE-2021-41307: Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to view the names of private projects and

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to view the names of private projects and private filters via an Insecure Direct Object References (IDOR) vulnerability in the Workload Pie Chart Gadget. The affected versions are before version 8.13.12, and from version 8.14.0 before 8.20.0.

HighCVSS 7.5 · v3.1—No exploit No fix recorded

Published: Oct 26, 2021
Updated: Jun 17, 2026
EPSS: 1.6% · 76th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
atlassian	jira	cpe:2.3:a:atlassian:jira
atlassian	jira server	cpe:2.3:a:atlassian:jira_server
atlassian	jira software data center	cpe:2.3:a:atlassian:jira_software_data_center

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

atlassian jirabefore 8.13.12
atlassian jira server8.14.0 and later · before 8.20.0
atlassian jira software data centerbefore 8.13.12
atlassian jira software data center8.14.0 and later · before 8.20.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

Atlassian Jira Data Center
- unspecified and later · before 8.13.12affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.0affected
Atlassian Jira Server
- unspecified and later · before 8.13.12affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.0affected

Same product

atlassian: all records

Other highest-scoring records for the same primary product.

CVE-2019-8442The CachingResourceDownloadRewriteRule class in Jira before version 7.13.4, and from version 8.0.0 before version 8.0.4, and from version 8.
48Plan
CVE-2019-8449The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information
46Plan
CVE-2017-5983The JIRA Workflow Designer Plugin in Atlassian JIRA Server before 6.3.0 improperly uses an XML parser and deserializer, which allows remote
44Plan

Published before and after this one in the same product

← EarlierCVE-2021-41305Oct 26, 2021 · Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view the names of private projects and filter
30Monitor
← EarlierCVE-2021-41306Oct 26, 2021 · Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to view private project and filter names via an
30Monitor
Later →CVE-2021-41308Oct 26, 2021 · Affected versions of Atlassian Jira Server and Data Center allow authenticated yet non-administrator remote attackers to edit the File Repli
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

AtlassianBugcrowd · paid · up to $12,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-21-0872 · Oct 27, 2021(Atlassian Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

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

nvd-primary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

jira.atlassian.com/browse/JRASERVER-72916

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records