-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 10.0.0, 10.1.0, 10.0.1, 10.0.2, 10.0.3, 10.2.0, 10.1.1, 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
-
Component/s: None
-
7.5
-
High
-
CVE-2026-45416
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
-
DoS (Denial of Service)
-
Bamboo Data Center
This High severity DoS (Denial of Service) vulnerability was introduced in versions 10.0.0, 10.1.0, 10.2.0, 11.0.0, 12.0.0, and 12.1.0 of Bamboo Data Center.
This DoS (Denial of Service) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H allows an unauthenticated attacker to cause a resource to be unavailable for its intended users by temporarily or indefinitely disrupting services of a host connected to a network which has no impact to confidentiality, no impact to integrity, high impact to availability, and requires no user interaction.
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.21
- Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.9
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 is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, SslClientHelloHandler.decode() reads the 24-bit TLS handshake length and, when the ClientHello does not fit in the first record, eagerly allocates `ctx.alloc().buffer(handshakeLength)` (line 161). The guard at line 140 is `handshakeLength > maxClientHelloLength && maxClientHelloLength != 0`, and the commonly-used SniHandler/AbstractSniHandler constructors (SniHandler(Mapping), SniHandler(AsyncMapping), AbstractSniHandler()) pass maxClientHelloLength=0 and handshakeTimeoutMillis=0, so the length guard is disabled and no timeout is scheduled. A 16 MiB request exceeds the default pooled chunk size and becomes a huge/unpooled allocation performed immediately. The buffer is retained in the handler until the channel closes. Versions 4.1.135.Final and 4.2.15.Final patch the issue.