Outdated Atlassian Confluence or Jira
A self-managed Confluence or Jira installation runs a release older than those fixing published Atlassian security advisories, some of which are actively exploited.
| Severity | Critical |
| CVSS 3.1 | 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application, T1213.001 Confluence |
| Category | Outdated Components |
Description
A self-managed installation of Atlassian Confluence or Jira is running a release that predates fixes published in Atlassian's security advisories, or a release that Atlassian no longer supports. These products are attractive targets because they are often reachable from the internet and hold an organisation's internal documentation and project information, and frequently credentials pasted into pages or tickets.
The most serious flaws let an unauthenticated attacker, from anywhere the application can be reached, run commands on the server with the privileges of the Confluence or Jira service, or create an administrator account. Confluence in particular has had several critical flaws of this kind, including the OGNL injection flaws CVE-2021-26084 and CVE-2022-26134, the template injection flaw CVE-2023-22527, and the access control flaws CVE-2023-22515 and CVE-2023-22518, which allowed attackers to create administrator accounts. All of these have been exploited in real attacks. Jira has also had critical flaws, such as the template injection flaw CVE-2019-11581, alongside regular fixes for server-side request forgery, information disclosure and cross-site scripting.
Command execution or an administrator account gives access to all of the content the instance holds, including restricted spaces and projects, any credentials or sensitive documents stored in it, and its local user accounts, and the server can then be used as a foothold into the internal network; compromised Confluence servers have been used to deploy ransomware. Instances reachable from the internet are at the greatest risk, as exploitation of these flaws has been automated and widespread soon after disclosure, but internal instances remain exposed to anyone who can reach them on the network.
The version is usually visible without authentication, in the footer and page metadata of Confluence and in the footer and the /rest/api/2/serverInfo endpoint of Jira, and is compared with the affected and fixed releases in each advisory. Fixes are delivered in new releases, and Atlassian's security bug fix and end of life policies set which release lines receive them. Atlassian has also ended support for its Server products, so an instance on a Server licence no longer receives security fixes at all.
Remediation
Upgrade to a supported, fixed release and keep to a regular update cycle:
- Upgrade Confluence and Jira to the latest release of a supported Long Term Support line, or to the latest feature release, as listed in Atlassian's security advisories. Do not remain on a release that has reached end of life, as it will not receive fixes.
- Where the instance runs on a Server licence, plan the move to a supported self-managed edition or to Atlassian's cloud service, because Server products no longer receive security fixes.
- Subscribe to Atlassian's security advisories and treat critical advisories for internet-facing instances as emergencies, applying the fix or the published mitigation within days.
- Keep installed Marketplace apps up to date as well, as they run inside the application and receive their own fixes.
As an interim measure, remove direct internet access to the instance, or place it behind a VPN or an authenticating reverse proxy until it is upgraded, and apply any temporary mitigation that Atlassian publishes for a specific flaw. Because the most serious flaws have been exploited at scale, an instance that ran a vulnerable release while reachable from the internet should be checked for signs of compromise, such as unexpected administrator accounts, new files in the installation directory and unusual processes started by the service account. Confirm the fix by checking the version shown by the application against the fixed releases in each relevant advisory.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.