安全缺陷修复政策
Atlassian 致力于确保客户系统不会因为 Atlassian 产品中漏洞遭到利用而受到损害，并将其作为一项首要任务。
范围
This policy describes how and when we may resolve security vulnerabilities in our products.
安全缺陷修复服务级别目标 (SLO)
Atlassian sets service level objectives for fixing security vulnerabilities based on the security severity level and the affected product. We've defined the following timeframe objectives for fixing security issues in our products:
Accelerated Resolution Objectives
These timeframes apply to all cloud-based Atlassian products, and any other software or system that is managed by Atlassian, or is running on Atlassian infrastructure. They also apply to Jira Align (both the cloud and self-managed releases).
- Critical vulnerabilities to be fixed in product within 10 days of being verified
- High vulnerabilities to be fixed in product within 28 days of being verified
- Medium vulnerabilities to be fixed in product within 84 days of being verified
- Low vulnerabilities to be fixed in product within 175 days of being verified
延期解决时限
These timeframe objectives apply to all self-managed Atlassian products. A self-managed product is installed by customers on customer-managed systems and includes Atlassian's Data Center and mobile apps.
- Critical, High, and Medium vulnerabilities to be fixed in product within 90 days of being verified
- Low vulnerabilities to be fixed in product within 180 days of being verified
严重漏洞
When a critical vulnerability is discovered by Atlassian or reported by a third party, Atlassian will take the following actions:
- For cloud products, we will ship a new fixed release for the affected product as soon as possible
- For self-managed products, we will:
- ship a bug fix release for the latest feature release of the affected product
- ship a new feature release for the affected product on the release schedule
- ship a bug fix release for all supported LTS releases of the affected product, in accordance with the Atlassian Support End of Life Policy.
产品 | 向后移植策略 | 示例 |
|---|---|---|
| Jira Software Server 和 Data Center Jira Core Server 和 Data Center Jira Service Management Server 和 Data Center（前身为 Jira Service Desk） | 为以下版本发布新的缺陷修复版本：
| 例如，如果 2020 年 1 月 1 日开发了严重安全缺陷的修复程序，则需要生成下列新的缺陷修复版本：
|
| Confluence Server 和 Data Center | 为以下版本发布新的缺陷修复版本：
| 例如，如果 2020 年 1 月 1 日开发了严重安全缺陷的修复程序，则需要生成下列新的缺陷修复版本：
|
| Bitbucket Server 和 Data Center | 为以下版本发布新的缺陷修复版本：
| 例如，如果 2020 年 1 月 1 日开发了严重安全缺陷的修复程序，则需要生成下列新的缺陷修复版本：
Bitbucket 6.3.0 发布于 2019 年 5 月 14 日，距离修复日期超过了 6 个月。如果它已被指定为“长期支持”版本，则也会生成缺陷修复版本。 |
| 我们只会为当前和上一功能版本发布新的缺陷修复版本。 | 例如，如果 2020 年 1 月 1 日为 Bamboo 开发了严重安全缺陷的修复程序，则需要生成下列新的缺陷修复版本：
|
For Crowd, Fisheye, and Crucible, we will provide a bug fix release for the latest feature release of the affected product.
Examples of critical vulnerability fixes for self-managed products:
If a critical vulnerability fix is developed on Feb 1, 2024, the following are example releases that would receive the bug fix:
产品 | 示例 |
|---|---|
| Jira Software | 示例 Jira Software 9.13.x because 9.13.0 is the latest feature release |
| 示例 Jira Software 9.12.x because 9.12.0 is the latest Long Term Support release | |
| 示例 Jira Software 9.4.x because 9.4.0 is the previous Long Term Support release | |
| Jira Service Management | 示例 Jira Service Management 5.13.x because 5.13.0 is the latest feature release |
| 示例 Jira Service Management 5.12.x because 5.12.0 is the latest Long Term Support release | |
| 示例 Jira Service Management 5.4.x because 5.4.0 is the second latest supported Long Term Support release | |
| Confluence | 示例 Confluence 8.7.x because 8.7.0 is the latest feature release |
| 示例 Confluence 8.5.x because 8.5.0 is the latest Long Term Support release | |
| 示例 Confluence 7.19.x because 7.19.0 is the second latest supported Long Term Support release | |
| Bitbucket | 示例 Bitbucket 8.17.x because 8.17.0 is the latest feature release |
| 示例 Bitbucket 8.9.x because 8.9.0 is the latest Long Term Support release | |
| 示例 Bitbucket 7.21.x because 7.21.0 is the second latest supported Long Term Support release | |
| Bamboo | 示例 Bamboo 9.5.x because 9.5.0 is the latest feature release |
| 示例 Bamboo 9.2.x because 9.2.0 is the latest Long Term Support release | |
| Crowd | 示例 Crowd 5.3.x because 5.3.0 is the latest feature release |
| Fisheye/Crucible | 示例 Fisheye/Crucible 4.8.x because 4.8.0 is the latest feature release |
No other product versions would receive new bug fixes.
Frequent upgrades ensure that your product instances are secure. It's a best practice to stay on the latest bug fix release of the latest feature release or LTS release of your product.
非严重漏洞
When a security issue of a High, Medium, or Low severity is discovered, Atlassian will aim to release a fix within the service level objectives listed at the beginning of this document. The fix may also be backported to Long Term Support releases, if feasible. The feasibility of backporting depends on complex dependencies, architectural changes, and compatibility, among other factors.
有缺陷修复版本可用时，应升级您的安装，以确保应用最新的安全修复程序。
其他信息
The severity level of vulnerabilities is calculated based on Severity Levels for Security Issues.
We'll continuously evaluate our policies based on customer feedback and will provide any updates or changes on this page.