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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAtlassian Jira Data Center
APPAtlassian6.3.0 – 8.5.16 (excl.)8.6.0 – 8.13.8 (excl.)8.14.0 – 8.17.0 (excl.)Atlassian Jira Service Desk
APPAtlassian2.0.2 – 4.5.16 (excl.)4.6.0 – 4.13.8 (excl.)Atlassian Jira Service Management
APPAtlassian4.14.0 – 4.17.0 (excl.)
Related vulnerabilities
Atlassian Jira Service Management — ominięcie uwierzytelnienia (Auth Bypass)
Atlassian — pominięcie Servlet Filters umożliwia auth bypass i XSS
Atlassian Jira Seraph – Auth Bypass przez spreparowane żądanie HTTP
XXE w Terracotta Quartz Scheduler — atak przez opis zadania XML
This High severity Path Traversal (Arbitrary Write) vulnerability was introduced in versions: 9.12.0, 10.3.0 a...