dbcve.org
JiraApplication · Atlassian

CVE-2019-8443

HIGH · 8.1 CVSS v3.1 Published 2019-05-22
Fix available
A fix is available. Upgrade to 7.13.4 / 8.0.4 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The ViewUpgrades resource in Jira before version 7.13.4, from version 8.0.0 before version 8.0.4, and from version 8.1.0 before version 8.1.1 allows remote attackers who have obtained access to administrator's session to access the ViewUpgrades administrative resource without needing to re-authenticate to pass "WebSudo" through an improper access control vulnerability.

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 confidence

Jira contains an improper access control vulnerability in the ViewUpgrades resource that allows remote attackers who have obtained access to an administrator's session to access the ViewUpgrades administrative resource without needing to re-authenticate through WebSudo, bypassing the secondary authentication mechanism.

MitigationUpgrade Jira to version 7.13.4, 8.0.4, 8.1.1 or later. If immediate patching is not possible, restrict administrative session access and monitor for unauthorized administrative actions.

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
JiraApplication
Affected:< 7.13.4
Jira ServerApplication
Affected:>= 8.0.0, < 8.0.4>= 8.1.0, < 8.1.1

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Jira version
    Access Jira administration menu or check the Jira installation directory for the version file. In the web UI, go to Administration > System > Troubleshooting and support > System Info to view the installed version.
    Affected if The version number is less than 7.13.4, OR between 8.0.0 and 8.0.4 inclusive, OR between 8.1.0 and 8.1.1 inclusive.
  2. Confirm Jira deployment type
    Determine whether the instance is Jira (cloud or data center before 8.0) or Jira Server (on-premises 8.x). Check the product name in System Info or the application banner.
    Affected if The instance is Atlassian Jira versions below 7.13.4 or Atlassian Jira Server versions 8.0.0-8.0.4 or 8.1.0-8.1.1.
  3. Verify WebSudo is enabled
    Go to Administration > Security Settings > Web Authentication or check the active security configuration. Confirm that WebSudo (secondary authentication for administrative actions) is turned on.
    Affected if WebSudo is enabled and the Jira version falls within the affected ranges, making the bypass applicable.
  4. Review audit logs for ViewUpgrades access
    Check Jira audit logs in Administration > System > Audit Log for any access to the ViewUpgrades resource. Look for administrative upgrade-related requests that did not trigger WebSudo re-authentication.
    Affected if There are ViewUpgrades resource accesses recorded without corresponding WebSudo authentication events in the audit trail.

A user is affected if their Jira installation runs version 7.13.4 or earlier, or version 8.0.0 through 8.0.4, or version 8.1.0 through 8.1.1, and WebSudo secondary authentication can be bypassed on the ViewUpgrades administrative endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 7.13.4 / 8.0.4 / 8.1.1 or later
Fixed in 7.13.48.0.48.1.1
Interim mitigation

Upgrade Jira to version 7.13.4, 8.0.4, 8.1.1 or later. If immediate patching is not possible, restrict administrative session access and monitor for unauthorized administrative actions.

Fix this in Jira Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8443 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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