-
Type:
Public Security Vulnerability
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 9.6.0, 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, 9.6.18, 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.0.0-rc3, 12.1.1, 10.2.13, 10.2.14, 10.2.15, 12.1.2, 12.1.3, 10.2.16
-
Component/s: None
-
8.7
-
High
-
CVE-2026-33871
-
Atlassian (Internal)
-
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
-
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 8.7 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N 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.
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.18
- Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.6
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 an asynchronous, event-driven network application framework. In versions prior to 4.1.132.Final and 4.2.10.Final, a remote user can trigger a Denial of Service (DoS) against a Netty HTTP/2 server by sending a flood of `CONTINUATION` frames. The server's lack of a limit on the number of `CONTINUATION` frames, combined with a bypass of existing size-based mitigations using zero-byte frames, allows an user to cause excessive CPU consumption with minimal bandwidth, rendering the server unresponsive. Versions 4.1.132.Final and 4.2.10.Final fix the issue.