JiraApplication · Atlassian
CVE-2018-13391
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 ProfileLinkUserFormat component of Jira Server before version 7.6.8, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3, from version 7.10.0 before version 7.10.3 and from version 7.11.0 before version 7.11.2 allows remote attackers who can access & view an issue to obtain the email address of the reporter and assignee user of an issue despite the configured email visibility setting being set to hidden.
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 confidenceThe ProfileLinkUserFormat component in Jira Server fails to respect the email visibility setting configured to hide user email addresses. An attacker who can view an issue (even with limited access) can obtain the email addresses of the reporter and assignee, bypassing the intended privacy controls.
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.6.8
Jira ServerApplication
>= 7.7.0, < 7.7.5>= 7.8.0, < 7.8.5>= 7.9.0, < 7.9.3>= 7.10.0, < 7.10.3>= 7.11.0, < 7.11.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/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.
-
Identify installed Jira versionCheck the Jira application version by accessing /rest/api/2/serverInfo or looking at the footer of any Jira pageAffected if The installed version falls within < 7.6.8, OR >= 7.7.0 and < 7.7.5, OR >= 7.8.0 and < 7.8.5, OR >= 7.9.0 and < 7.9.3, OR >= 7.10.0 and < 7.10.3, OR >= 7.11.0 and < 7.11.2
-
Verify email visibility setting configurationNavigate to Administration > User Management > User Privacy or check the 'Hide Email Addresses' setting in Jira global settingsAffected if Email visibility is configured to hide addresses but is not being respected by the ProfileLinkUserFormat component
-
Confirm ProfileLinkUserFormat is in useInspect issue views (particularly reporter and assignee fields) in the web interface or via REST API to see if user profile links are displayedAffected if User profile links containing email addresses appear in issue views despite privacy settings
-
Test issue access with limited userCreate or use a test account with minimal issue view permissions and attempt to view an issue where the reporter/assignee email should be hiddenAffected if The limited user can see the email addresses of reporters or assignees in the issue view
A user is affected if their Jira Server version is within the affected ranges AND they have users with email visibility restrictions configured AND limited-access users can view reporter/assignee email addresses in issues.
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.6.87.7.57.8.5
Upgrade Jira Server to version 7.6.8, 7.7.5, 7.8.5, 7.9.3, 7.10.3, 7.11.2 or later. As a temporary mitigation, restrict issue view access to only trusted users until the upgrade can be completed.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13391 — 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-2018-13391 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