This High severity Improper Authorization vulnerability was introduced in versions 7.4.0, 7.13.0, 8.5.0, 8.9.0, 9.0.1…
Atlassian Confluence Data Center
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Atlassian Confluence Data Center |
|
|
Atlassian Confluence Data Center
| Product | Affected | Fixed in |
|---|---|---|
| Atlassian Confluence Data Center |
|
|
This High severity Improper Authorization vulnerability was introduced in versions 7.4.0, 7.13.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0, and 10.2.0 of Confluence Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Confluence Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Confluence Data Center 9.2: Upgrade to a release greater than or equal to 9.2.24 Confluence Data Center 10.2: Upgrade to a release greater than or equal to 10.2.17 See the release notes ([https://confluence.atlassian.com/doc/confluence-release-notes-327.html]). You can download the latest version of Confluence Data Center from the download center ([https://www.atlassian.com/software/confluence/download-archives]). This vulnerability was reported via our Penetration Testing program.
From the CVE record · atlassian
Confluence Data Center has an improper authorization vulnerability. An authenticated attacker can gain unintended access to resources or functionality, potentially exposing sensitive information or enabling arbitrary code execution. The input does not specify whether the attack requires network or local access or any user interaction.
Teams running Confluence Data Center should check instances on versions 7.4.0, 7.13.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0, or 10.2.0, in which the vulnerability was introduced.