JiraApplication · Atlassian
CVE-2019-3402
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 ConfigurePortalPages.jspa resource in Jira before version 7.13.3 and from version 8.0.0 before version 8.1.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the searchOwnerUserName 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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in Atlassian Jira's ConfigurePortalPages.jspa resource. Attackers can inject arbitrary HTML or JavaScript through the searchOwnerUserName parameter, potentially allowing session hijacking or credential theft against users who access malicious links.
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
< 7.13.3
Jira ServerApplication
>= 8.0.0, < 8.1.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Jira installation directoryIdentify the base directory where Jira software is installed on your server. This is typically the directory containing atlassian-jira folder or the installation path used during setup.Affected if Installation directory cannot be located - version check may be incomplete
-
Identify the installed Jira versionCheck the Jira version by logging into Jira as an administrator and navigating to Administration > System > System Info, or by inspecting the pom.xml or version files in the installation directory.Affected if Unable to determine the exact installed version from the system information page or installation files
-
Compare against affected version rangesReview the identified version against the vulnerable ranges: versions < 7.13.3 OR versions >= 8.0.0 and < 8.1.1. Note that versions 7.13.3 through 7.x.x and 8.1.1 and later are NOT affected.Affected if The installed version falls within < 7.13.3 or >= 8.0.0 but < 8.1.1
-
Verify ConfigurePortalPages.jspa accessibilityConfirm the /ConfigurePortalPages.jspa endpoint is accessible. This endpoint is typically found under /secure/ConfigurePortalPages.jspa and is generally restricted to administrator users, but the XSS can still trigger when an admin clicks a malicious link.Affected if Endpoint is accessible to users (even admins) and version is in the affected range
Your environment is affected if the installed Jira version is less than 7.13.3 OR is 8.0.0 through 8.1.0, regardless of whether the ConfigurePortalPages.jspa endpoint is publicly accessible.
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.
From vendor data7.13.38.1.1
Upgrade Jira to version 7.13.3 or later, or version 8.1.1 or later. Alternatively, apply the vendor-supplied patch for affected versions.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3402 — 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-2019-3402 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