{"uuid": "ccc96950-ac5e-4a70-bdb2-e8576df37d96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2020-36239", "type": "seen", "source": "https://t.me/hacking_Attack/17478", "content": "Black Hat Ethical Hacking\nCritical Jira Flaw in Atlassian Could Lead to RCE\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Critical Jira Flaw in Atlassian Could Lead to RCEPost Views: 96 \nReading Time: 2 Minutes\nAtlassian has dropped a patch for a critical vulnerability in many versions of its Jira Data Center and Jira Service Management Data Center products, which can lead to arbitrary code execution.\nAtlassian is a platform that\u2019s used by 180,000 customers to engineer software and manage projects, and Jira is its proprietary bug-tracking and agile project-management tool.\n\nOn Wednesday, Atlassian issued a security advisory concerning the vulnerability, which is tracked as CVE-2020-36239. The bug could enable remote, unauthenticated attackers to execute arbitrary code in some Jira Data Center products. BleepingComputer\u00a0got ahold of an email Atlassian sent to enterprise customers on Wednesday that urged them to update ASAP.\n\nThe vulnerability has to do with a missing authentication check in Jira\u2019s implementation of Ehcache, which is an open-source, Java distributed cache for general-purpose caching, Java EE and lightweight containers that\u2019s used for performance and which simplifies scalability.\n\nAtlassian said that the bug was introduced in version 6.3.0 of Jira Data Center, Jira Core Data Center, Jira Software Data Center and Jira Service Management Data Center (known as Jira Service Desk prior to 4.14).\n\nAccording to Atlassian\u2019s security advisory, that list of products exposed a Ehcache remote method invocation (RMI) network service that attackers \u2013 who can connect to the service on port 40001 and potentially 40011 \u2013 could use to \u201cexecute arbitrary code of their choice in Jira\u201d through deserialization, due to missing authentication.\n\nRMI is an API that acts as a mechanism to enable remote communication between programs written in Java. It allows an object residing in one Java virtual machine (JVM) to invoke an object running on another JVM; Often, it involves one program on a server and one on a client. The advantage of RMI, as BleepingComputer describes it, is that \u201cprogrammers can invoke methods present in remote objects\u2014such as those present within an application running on a shared network, right from their application as they would run a local method or procedure.\u201d https://media.threatpost.com/wp-content/uploads/sites/103/2021/07/22161351/RMI.png Workings of RMI. Source: Wikipedia.\nSee Also: Microsoft: New Unpatched Bug in Windows Print Spooler\nAtlassian \u201cstrongly suggests\u201d restricting access to the Ehcache ports to only Data Center instances, but noted that there\u2019s a caveat: \u201cFixed versions of Jira will now require a shared secret in order to allow access to the Ehcache service,\u201d according to the advisory. Affected VersionsThese are the affected versions of Jira Data Center and Jira Service Management Data Center: Jira Data Center, Jira Core Data Center, and Jira Software Data Center \u2013 ranges* 6.3.0 <=\n* 8.6.0 <=\n* 8.14.0 <= Jira Service Management Data Center \u2013 ranges* 2.0.2 <=\n* 4.6.0 <=\n* 4.14.0 <= Jira Data Center, Jira Core Data Center, and Jira Software Data Center* All 6.3.x, 6.4.x versions\n* All 7.0.x, 7.1.x , 7.2.x, 7.3.x, 7.4.x, 7.5.x, 7.6.x, 7.7.x, 7.8.x, 7.9.x, 7.10.x, 7.11.x, 7.12.x, 7.13.x versions\n* All 8.0.x, 8.1.x, 8.2.x, 8.3.x, 8.4.x versions\n* All 8.5.x versions before 8.5.16\n* All 8.6.x, 8.7.x, 8.8.x, 8.9.x, 8.10.x, 8.11.x, 8.12.x versions\n* All 8.13.x versions before 8.13.8\n* All 8.14.x, 8.15.x, 8.16.x versions Jira Service Management Data Center* All 2.x.x versions after 2.0.2\n* All 3.x.x versions\n* All 4.0.x, 4.1.x, 4.2.x, 4.3.x, 4.4.x ve[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-08T00:00:11.284297Z"}