Jira AlignApplication · Atlassian
CVE-2022-36803
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe MasterUserEdit API in Atlassian Jira Align Server before version 10.109.2 allows An authenticated attacker with the People role permission to use the MasterUserEdit API to modify any users role to Super Admin. This vulnerability was reported by Jacob Shafer from Bishop Fox.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a privilege escalation vulnerability in Jira Align Server's MasterUserEdit API. An authenticated attacker with only the basic People role permission can call this API to modify any user's role to Super Admin, effectively achieving maximum privileges on the platform.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Jira AlignApplication
< 10.109.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Jira Align Server installationIdentify if Jira Align Server is deployed in your environment. Check your application inventory or running services for Atlassian Jira Align.Affected if Jira Align Server is not installed - not affected. If installed, proceed to version check.
-
Check installed Jira Align versionLocate the Jira Align Server version information, typically found in the application UI (often under About or Administration > System), or check the installation files/database for the version number.Affected if Version is lower than 10.109.2 - environment is potentially affected by this vulnerability.
-
Verify MasterUserEdit API accessibilityDetermine if the MasterUserEdit API endpoint is exposed and accessible in your environment. This API allows user role modifications.Affected if API is exposed without additional authorization controls beyond basic People role permission - environment is vulnerable.
-
Review user role modificationsCheck application audit logs, user management logs, or security event logs for any role changes to Super Admin performed by users with only basic People role permissions.Affected if Unauthorized role escalations to Super Admin are found in logs - exploitation has occurred.
-
Audit Super Admin accountsReview the list of Super Admin accounts in Jira Align and verify that all escalations were performed by authorized administrators.Affected if Unexpected Super Admin accounts exist that were not created through proper admin channels - potential exploitation detected.
Environment is affected if Jira Align Server version is below 10.109.2 AND the MasterUserEdit API is accessible to users with only basic People role permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.109.2
Upgrade Jira Align Server to version 10.109.2 or later, which contains the fix for this authorization bypass in the MasterUserEdit API.
Jira Align Server 10.109.2 or later
- 1. Identify the current Jira Align Server version in your environment
- 2. Create a full backup of your Jira Align instance including the database
- 3. Upgrade Jira Align Server to version 10.109.2 or later
- 4. Verify the upgrade completed successfully by checking the version in About Jira Align
- 5. Confirm that the MasterUserEdit API no longer allows users with only People role to escalate privileges to Super Admin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jira Align
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36803 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data