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.

Vulnerability/
CVE-2017-18033

medium

6.5

CWE

352

18/1/2018

17/9/2024

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

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.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/severity
agent/author
agent/weakness
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
vendor/atlassian
canonical/atlassian jira

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.