CVE-2018-5232: XSS
First published: Wed Jul 18 2018(Updated: )
The EditIssue.jspa resource in Atlassian Jira before version 7.6.7 and from version 7.7.0 before version 7.10.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the issuetype parameter.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Core | <7.6.7 | |
| Atlassian Server | >=7.7.0<7.10.1 |
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
Frequently Asked Questions
What is the severity of CVE-2018-5232?
CVE-2018-5232 is considered a medium severity vulnerability due to its potential for cross site scripting (XSS) attacks.
How do I fix CVE-2018-5232?
To remediate CVE-2018-5232, you should upgrade Atlassian Jira to version 7.6.7 or to any version above 7.10.1.
What types of attacks can CVE-2018-5232 facilitate?
CVE-2018-5232 can enable remote attackers to execute arbitrary HTML or JavaScript in users' browsers.
Which versions of Atlassian Jira are affected by CVE-2018-5232?
CVE-2018-5232 affects Atlassian Jira versions before 7.6.7 and versions between 7.7.0 and 7.10.1.
What mitigations are available for CVE-2018-5232 if an upgrade cannot be performed?
If immediate upgrades cannot be performed, implement input validation and output encoding to mitigate the XSS risk associated with CVE-2018-5232.
- agent/type
- agent/softwarecombine
- agent/author
- agent/weakness
- agent/references
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian jira core
- canonical/atlassian server
- version/atlassian server/7.7.0