-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 10.1.0, 10.2.0, 11.0.0, 10.2.1, 10.2.2, 10.2.3, 12.0.0, 10.2.4, 11.0.1, 10.2.5, 11.0.2, 11.0.3, 10.2.6, 10.2.7, 11.0.4, 12.1.0, 10.2.8, 11.0.5, 10.2.9, 11.0.7, 11.0.8, 10.2.10, 10.2.11, 12.0.1, 12.0.2, 10.2.12, 12.1.1, 10.2.13, 10.2.14, 10.2.15, 12.1.2, 12.1.3, 10.2.16, 10.2.18, 11.1.0, 12.1.6, 12.1.7, 10.2.19, 12.1.8, 10.2.17, 10.2.20, 10.2.21, 12.1.9, 12.1.10, 10.2.22, 12.1.4, 12.1.5
-
Component/s: None
-
8.7
-
High
-
CVE-2026-62243
-
Atlassian (Internal)
-
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
-
BASM (Broken Authentication & Session Management)
-
Bamboo Data Center
This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.1.0, 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.
This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N allows an unauthenticated attacker to perform actions as another user.
Atlassian recommends that Bamboo 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:
- Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.23
- Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.11
See the release notes (https://confluence.atlassian.com/bambooreleases/bamboo-release-notes-1189793869.html). You can download the latest version of Bamboo Data Center from the download center (https://www.atlassian.com/software/bamboo/download-archives).
The National Vulnerability Database provides the following description for this vulnerability: Netty (io.netty:netty-handler) versions from 4.2.0.Final through 4.2.16.Final and versions through 4.1.136.Final disable TLS hostname verification on the SslProvider.OPENSSL client path when a plain (non-extended) X509TrustManager is used and Unsafe-based trust-manager wrapping is unavailable (Java 25+). In this configuration the OpenSSL client does not perform hostname verification, allowing a man-in-the-middle attacker to present a certificate issued for a different hostname that is accepted without validation. Fixed in 4.2.17.Final and 4.1.137.Final.