This issue exists to document that a security improvement in the way that Jira Server and Data Center use velocity templates has been implemented. The way in which velocity templates were used in Atlassian Jira Server and Data Center in affected versions allowed remote attackers to achieve remote code execution via insecure deserialization, if they were able to exploit a server side template injection vulnerability. The affected versions are before version 7.13.0, from version 8.0.0 before 8.5.0, and from version 8.6.0 before version 8.8.1.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jira | Atlassian | * | 7.13.0 (excluding) |
| Jira | Atlassian | 8.0.0 (including) | 8.5.0 (excluding) |
| Jira | Atlassian | 8.6.0 (including) | 8.8.1 (excluding) |
| Jira_software_data_center | Atlassian | * | 7.13.0 (excluding) |
| Jira_software_data_center | Atlassian | 8.0.0 (including) | 8.5.0 (excluding) |
| Jira_software_data_center | Atlassian | 8.6.0 (including) | 8.8.1 (excluding) |
It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.