Bamboo 8.0
Bamboo 8.0
The Bamboo 8.0 reached end of service life on Mar 28, 2023 — Bamboo no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Bamboo 8.0 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- bamboo
- release
- 8.0
- product Label
- Bamboo
- release Label
- 8.0
- codename
- lts
- latest Version
- 8.0.13
- release Date
- 2021-07-29
- maintained
- source Url
- https://endoflife.date/bamboo
Lifecycle Dates
- End of Service Life
- Mar 28, 2023
- Last OEM Support
- Mar 28, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Bamboo 8.0 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Bamboo 8.0?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Bamboo 8.0 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Bamboo 8.0 Support: Frequently Asked Questions
Is the Bamboo 8.0 still supported?
Bamboo ended support for the Bamboo 8.0 on Mar 28, 2023 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Bamboo 8.0 end of service life (EOSL) date?
Bamboo lists the end of service life for the Bamboo 8.0 as Mar 28, 2023.
Can I keep using the Bamboo 8.0 after its EOSL date?
Yes. EOSL means Bamboo stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Bamboo 8.0 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Bamboo 8.0
2 published CVEs affect the Bamboo 8.0, including 2 rated critical or high severity. Bamboo no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2022-26136 | CRITICAL | 9.8 | Jul 20, 2022 | A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used by first and third party apps. The impact depends on which filters are used by each app, and how the filters are used. This vulnerability can result in authentication bypass and cross-site scripting. Atlassian has released updates that fix the root cause of this vulnerability, but has not exhaustively enumerated all potential consequences of this vulnerability. Atlassian Bamboo |
| CVE-2022-26137 | HIGH | 8.8 | Jul 20, 2022 | A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet Filters to be invoked when the application processes requests or responses. Atlassian has confirmed and fixed the only known security issue associated with this vulnerability: Cross-origin resource sharing (CORS) bypass. Sending a specially crafted HTTP request can invoke the Servlet Filter used to respond to CORS requests, resulting in a CORS bypass. An attacker that can trick a |