CVE-2017-18033: CSRF
First published: Thu Jan 18 2018(Updated: )
The Jira-importers-plugin in Atlassian Jira before version 7.6.1 allows remote attackers to create new projects and abort an executing external system import via various Cross-site request forgery (CSRF) vulnerabilities.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira | <7.6.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-2017-18033?
CVE-2017-18033 has been classified as a medium severity vulnerability due to its potential for unauthorized project creation and interference with system imports.
How do I fix CVE-2017-18033?
To fix CVE-2017-18033, upgrade Atlassian Jira to version 7.6.1 or later which contains the necessary patches.
What types of attacks does CVE-2017-18033 enable?
CVE-2017-18033 enables remote attackers to perform Cross-site request forgery (CSRF) attacks that can create new projects and abort imports.
Which versions of Atlassian Jira are affected by CVE-2017-18033?
Atlassian Jira versions prior to 7.6.1 are affected by CVE-2017-18033.
How can I confirm if CVE-2017-18033 has been exploited?
You can check your Jira logs for unauthorized project creation or import aborts as potential indicators of exploitation of CVE-2017-18033.
- agent/references
- agent/type
- agent/severity
- agent/author
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian jira