Data CenterApplication · Atlassian
CVE-2021-39119
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 · uneditedAffected versions of Atlassian Jira Server and Data Center allow users who have watched an issue to continue receiving updates on the issue even after their Jira account is revoked, via a Broken Access Control vulnerability in the issue notification feature. The affected versions are before version 8.19.0.
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 confidenceA Broken Access Control vulnerability in Jira Server and Data Center's issue notification feature allows deactivated user accounts to continue receiving issue updates. When a user watches an issue, the system registers them for notifications, but upon account revocation, the watch/notification subscription is not invalidated, allowing revoked users to continue receiving sensitive issue updates.
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
Data CenterApplication
< 8.19.0
JiraApplication
< 8.19.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Check installed Jira versionLog in as an administrator and navigate to the Jira Administration page, or access the /about page endpoint. Locate the version number displayed (typically shown as 8.x.y). Compare this version to the affected range: versions prior to 8.19.0 are vulnerable.Affected if The installed Jira version is 8.18.x or earlier, or any 8.x.y version below 8.19.0.
-
Identify deactivated users with watch subscriptionsAccess the Jira database or use the administrator interface to query user accounts. Filter for user accounts in 'deactivated' or 'inactive' status. For each deactivated user, check if they have any issue watch subscriptions stored in the system.Affected if Any deactivated user account still has an active watch subscription on one or more issues in the system.
-
Verify notification subscriptions for revoked accountsUse the Jira administration console or database queries to examine the 'Notifications' or 'Watchers' table. Cross-reference the subscriber/user IDs against the list of deactivated accounts.Affected if Deactivated user accounts appear as active watchers or notification recipients for any issue.
Your environment is affected if Jira Server or Data Center is running version 8.19.0 or later - the vulnerability only impacts versions below 8.19.0, and only if deactivated users retain active issue watch subscriptions.
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 · scoped8.19.0
Upgrade Jira Server and Data Center to version 8.19.0 or later, which contains the fix for this broken access control issue.
8.19.0
- Backup your Jira database and home directory before upgrading
- Review the Atlassian Jira upgrade guide and release notes for version 8.19.0
- Ensure your system meets the requirements for Jira 8.19.0
- Upgrade your Jira Server or Data Center instance to version 8.19.0 or later
- After upgrade, verify that revoked user accounts no longer receive issue notifications by testing with a previously revoked user
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Data Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39119 — 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-2021-39119 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