CVE-2016-4318: XSS
First published: Mon Apr 10 2017(Updated: )
Atlassian JIRA Server before 7.1.9 has XSS in project/ViewDefaultProjectRoleActors.jspa via a role name.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira | <=7.1.8 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/97516
- https://confluence.atlassian.com/jiracore/jira-core-7-1-x-release-notes-802161668.html#JIRACore7.1.xreleasenotes-v7.1.9v7.1.9-06July2016
- https://jira.atlassian.com/browse/JRA-61861
- https://jira.atlassian.com/browse/JRASERVER-61861
- https://jira.atlassian.com/secure/ReleaseNote.jspa?projectId=10240&version=62034
Frequently Asked Questions
What is the severity of CVE-2016-4318?
CVE-2016-4318 is classified as a medium severity vulnerability due to its potential for XSS attacks.
How do I fix CVE-2016-4318?
To fix CVE-2016-4318, upgrade Atlassian JIRA Server to version 7.1.9 or later.
What does CVE-2016-4318 affect?
CVE-2016-4318 affects Atlassian JIRA Server versions prior to 7.1.9.
What type of vulnerability is CVE-2016-4318?
CVE-2016-4318 is an XSS (Cross-Site Scripting) vulnerability that affects JIRA regarding role names.
Is CVE-2016-4318 easy to exploit?
CVE-2016-4318 can be exploited by attackers who can control or manipulate project role names in JIRA.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/references
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian jira
- version/atlassian jira/7.1.8