Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0 before 8.17.0 and Jira Service Management Data Center from version 2.0.2 before 4.5.16, from version 4.6.0 before 4.13.8, and from version 4.14.0 before 4.17.0 exposed a Ehcache RMI network service which attackers, who can connect to the service, on port 40001 and potentially 40011[0][1], could execute arbitrary code of their choice in Jira through deserialization due to a missing authentication vulnerability. While Atlassian strongly suggests restricting access to the Ehcache ports to only Data Center instances, fixed versions of Jira will now require a shared secret in order to allow access to the Ehcache service. [0] In Jira Data Center, Jira Core Data Center, and Jira Software Data Center versions prior to 7.13.1, the Ehcache object port can be randomly allocated. [1] In Jira Service Management Data Center versions prior to 3.16.1, the Ehcache object port can be randomly allocated.
References
Link | Resource |
---|---|
https://jira.atlassian.com/browse/JRASERVER-72566 | Issue Tracking Vendor Advisory |
https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html | Patch Vendor Advisory |
https://jira.atlassian.com/browse/JSDSERVER-8454 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2021-07-29 04:15
Updated : 2022-08-01 09:32
NVD link : CVE-2020-36239
Mitre link : CVE-2020-36239
JSON object : View
CWE
CWE-306
Missing Authentication for Critical Function
Products Affected
atlassian
- jira_service_management
- jira_data_center
- jira_service_desk