# CVE-2021-43949: Missing authorization in Jira Service Management Data Center

> Authenticated attackers can view private objects in Jira Service Management due to broken access control in Custom Fields.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2022
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-6v7j-h4h2-4p86

## What is CVE-2021-43949?

CVE-2021-43949 is a medium-severity missing authorization vulnerability in Atlassian Jira Service Management Data Center, published on 10 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of Atlassian Jira Service Management Server and Data Center allow authenticated remote attackers to view private objects via a Broken Access Control vulnerability in the Custom Fields feature. The affected versions are before version 4.21.0.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Atlassian Jira Service Management.

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

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

## Is CVE-2021-43949 being exploited?

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

## Other vulnerabilities in Atlassian Jira Service Management Data Center

- [CVE-2023-22501](https://insights.sbomify.com/CVE-2023-22501/): Auth bypass in Jira Service Management Data Center (critical 9.4)
- [CVE-2021-43943](https://insights.sbomify.com/CVE-2021-43943/): Cross-site scripting in Jira Service Management Data Center (medium 4.8)
- [CVE-2022-36800](https://insights.sbomify.com/CVE-2022-36800/): Information disclosure in Jira Service Management Data Center (medium 4.3)
- [CVE-2021-43948](https://insights.sbomify.com/CVE-2021-43948/): Missing authorization in Jira Service Management Data Center (medium 4.3)
- [CVE-2021-43950](https://insights.sbomify.com/CVE-2021-43950/): Missing authorization in Jira Service Management Data Center (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43949 is a medium-severity missing authorization vulnerability in Atlassian Jira Service Management Data Center, published on 10 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43949 in the wild and no public exploit code.

Affected product: Atlassian Jira Service Management 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-43949/ (Markdown: https://insights.sbomify.com/CVE-2021-43949/index.md)
```

## Sources

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

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