# CVE-2021-41311: Auth bypass in Jira Data Center

> Attackers with revoked admin access can modify project roles in Atlassian Jira due to broken authentication, requiring an upgrade to fix.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2021
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-7fxq-g996-6g8m

## What is CVE-2021-41311?

CVE-2021-41311 is a high-severity authentication bypass vulnerability in Atlassian Jira Data Center, published on 8 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of Atlassian Jira Server and Data Center allow attackers with access to an administrator account that has had its access revoked to modify projects' Users & Roles settings, via a Broken Authentication vulnerability in the /plugins/servlet/project-config/PROJECT/roles endpoint. The affected versions are before version 8.19.1.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-41311?

It affects 1 product.


Products: Atlassian Jira Software Data Center.

## How do I fix CVE-2021-41311?

No fix has been published for CVE-2021-41311 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41311 being exploited?

There is no known exploitation of CVE-2021-41311 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira Data Center

- [CVE-2021-41310](https://insights.sbomify.com/CVE-2021-41310/): Cross-site scripting in Jira Data Center (medium 6.1)
- [CVE-2021-41309](https://insights.sbomify.com/CVE-2021-41309/): Auth bypass in Jira Data Center (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41311 and fix it if it is affected.

What it is: CVE-2021-41311 is a high-severity authentication bypass vulnerability in Atlassian Jira Data Center, published on 8 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41311 in the wild and no public exploit code.

Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41311/ (Markdown: https://insights.sbomify.com/CVE-2021-41311/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41311
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41311
- OSV: https://osv.dev/vulnerability/CVE-2021-41311

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41311/
Summaries are generated and may contain mistakes; the official description above is the record.