CVE-2020-36239
Last modified
CVE-2020-36239 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 48.88% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Atlassian | Jira Data Center | >= 6.3.0, < 8.5.16 |
| Atlassian | Jira Data Center | >= 8.6.0, < 8.13.8 |
| Atlassian | Jira Data Center | >= 8.14.0, < 8.17.0 |
| Atlassian | Jira Service Desk | >= 2.0.2, < 4.5.16 |
| Atlassian | Jira Service Desk | >= 4.6.0, < 4.13.8 |
| Atlassian | Jira Service Management | >= 4.14.0, < 4.17.0 |
References
- https://jira.atlassian.com/browse/JRASERVER-72566Issue Tracking, Vendor Advisory
- https://jira.atlassian.com/browse/JSDSERVER-8454Issue Tracking, Vendor Advisory
- https://jira.atlassian.com/browse/JRASERVER-72566Issue Tracking, Vendor Advisory
- https://jira.atlassian.com/browse/JSDSERVER-8454Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-36239?
How severe is CVE-2020-36239?
How do I fix CVE-2020-36239?
Are you affected by CVE-2020-36239?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
