CVE-2017-5983: Critical severity Atlassian Jira vulnerability
Published Apr 10, 2017
·Updated
The JIRA Workflow Designer Plugin in Atlassian JIRA Server before 6.3.0 improperly uses an XML parser and deserializer, which allows remote attackers to execute arbitrary code, read arbitrary files, or cause a denial of service via a crafted serialized Java object.
Affected Software
66 affected components
Atlassian Jira=4.2.4
Atlassian Jira=4.3
Atlassian Jira=4.3.1
Atlassian Jira=4.3.2
Atlassian Jira=4.3.3
Atlassian Jira=4.3.4
Atlassian Jira=4.4
Atlassian Jira=4.4.1
Atlassian Jira=4.4.2
Atlassian Jira=4.4.3
Atlassian Jira=4.4.4
Atlassian Jira=4.4.5
Atlassian Jira=5.0
Atlassian Jira=5.0.1
Atlassian Jira=5.0.2
Atlassian Jira=5.0.3
Atlassian Jira=5.0.4
Atlassian Jira=5.0.5
Atlassian Jira=5.0.7
Atlassian Jira=5.1
Atlassian Jira=5.1.1
Atlassian Jira=5.1.2
Atlassian Jira=5.1.3
Atlassian Jira=5.1.4
Atlassian Jira=5.1.5
Atlassian Jira=5.1.6
Atlassian Jira=5.1.7
Atlassian Jira=5.1.8
Atlassian Jira=5.2
Atlassian Jira=5.2.1
Atlassian Jira=5.2.2
Atlassian Jira=5.2.3
Atlassian Jira=5.2.4
Atlassian Jira=5.2.5
Atlassian Jira=5.2.6
Atlassian Jira=5.2.7
Atlassian Jira=5.2.8
Atlassian Jira=5.2.9
Atlassian Jira=5.2.10
Atlassian Jira=5.2.11
Atlassian Jira=6.0
Atlassian Jira=6.0.1
Atlassian Jira=6.0.2
Atlassian Jira=6.0.3
Atlassian Jira=6.0.4
Atlassian Jira=6.0.5
Atlassian Jira=6.0.7
Atlassian Jira=6.0.8
Atlassian Jira=6.1
Atlassian Jira=6.1.1
Atlassian Jira=6.1.2
Atlassian Jira=6.1.3
Atlassian Jira=6.1.4
Atlassian Jira=6.1.5
Atlassian Jira=6.1.6
Atlassian Jira=6.1.7
Atlassian Jira=6.1.8
Atlassian Jira=6.1.9
Atlassian Jira=6.2
Atlassian Jira=6.2.1
Atlassian Jira=6.2.2
Atlassian Jira=6.2.3
Atlassian Jira=6.2.4
Atlassian Jira=6.2.5
Atlassian Jira=6.2.6
Atlassian Jira=6.2.7
Event History
Apr 10, 2017
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:59 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5983?
CVE-2017-5983 is considered a critical vulnerability due to its potential for remote code execution.
2
How can I fix CVE-2017-5983?
To fix CVE-2017-5983, upgrade Atlassian JIRA to version 6.3.0 or later.
3
What types of attacks can exploit CVE-2017-5983?
CVE-2017-5983 can be exploited to execute arbitrary code, read files, or cause denial of service.
4
Which versions of Atlassian JIRA are affected by CVE-2017-5983?
CVE-2017-5983 affects Atlassian JIRA versions prior to 6.3.0.
5
Is CVE-2017-5983 being actively exploited?
Yes, there have been reports of active exploitation of CVE-2017-5983 in the wild.