dbcve.org
Jira ServerApplication · Atlassian

CVE-2019-3400

MEDIUM · 6.1 CVSS v3.1 Published 2019-05-03
Fix available
A fix is available. Upgrade to 7.13.2 / 8.0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 labels gadget in Jira before version 7.13.2, and from version 8.0.0 before version 8.0.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the jql parameter.

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

This is a reflected cross-site scripting (XSS) vulnerability in Atlassian Jira's labels gadget. The vulnerability exists in the jql parameter, allowing remote attackers to inject arbitrary HTML or JavaScript code that executes in the victim's browser when they interact with the affected component.

MitigationUpgrade Jira to version 7.13.2 or later, or version 8.0.2 or later to patch this vulnerability.

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 ServerApplication
Affected:< 7.13.2>= 8.0.0, < 8.0.2

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Determine your Jira Server version
    Check the Jira footer on any page or query the /rest/api/2/serverInfo endpoint
    Affected if The version displayed is less than 7.13.2, or is 8.0.0 or 8.0.1 (the affected ranges)
  2. Identify if labels gadget is accessible
    Navigate to a user dashboard and check if the Labels gadget is available to add, or inspect the gadget configuration endpoint
    Affected if The Labels gadget feature exists and can be configured on user dashboards
  3. Confirm gadget accepts jql parameter
    Access the Labels gadget configuration and inspect how the jql parameter is handled in the request
    Affected if The gadget accepts a jql parameter without proper sanitization in the response
  4. Check for reflected content in jql parameter
    Submit a test jql parameter value (such as a benign string) and observe if it reflects unchanged in the response HTML
    Affected if The jql parameter value reflects directly in the page without encoding

You are affected if your Jira Server version is below 7.13.2 or between 8.0.0-8.0.1 AND the Labels gadget is accessible to users who can add it to their dashboard.

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.2 / 8.0.2 or later
Fixed in 7.13.28.0.2
Interim mitigation

Upgrade Jira to version 7.13.2 or later, or version 8.0.2 or later to patch this vulnerability.

Fix this in Jira Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3400 — 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-3400 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