CVE-2017-18039: XSS
First published: Fri Feb 02 2018(Updated: )
The IncomingMailServers resource in Atlassian Jira from version 6.2.1 before version 7.4.4 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the messagesThreshold parameter.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira | >=6.2.1<7.4.4 |
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-2017-18039?
CVE-2017-18039 is considered a medium-severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2017-18039?
To fix CVE-2017-18039, upgrade Atlassian Jira to version 7.4.4 or later where the vulnerability has been patched.
What is the nature of the vulnerability in CVE-2017-18039?
CVE-2017-18039 is a cross-site scripting (XSS) vulnerability that allows remote attackers to inject arbitrary HTML or JavaScript.
Which versions of Atlassian Jira are affected by CVE-2017-18039?
Atlassian Jira versions from 6.2.1 to 7.4.3 are affected by CVE-2017-18039.
What can attackers do with CVE-2017-18039?
Attackers exploiting CVE-2017-18039 can inject scripts that may steal sensitive user data or perform actions on behalf of users unsuspectingly.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/weakness
- 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/6.2.1