Close

Security Bug Fix Policy


Scope

This policy describes how and when we may resolve security vulnerabilities in our products.

Security bug fix Service Level Objectives (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 14 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 42 days of being verified
  • Low vulnerabilities to be fixed in product within 175 days of being verified

 

Extended Resolution Timeframes

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

Critical Vulnerabilities

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.

 

Product
Back port policy
Example

Jira Software Server and Data Center

Jira Core Server and Data Center

Jira Service Management Server and Data Center (previously known as Jira Service Desk)

Issue new bug fix releases for:

  • Any versions designated an 'Long Term Support release' that have not reached end of life.
  • All feature versions released within 6 months of the date the fix is released.

For example, if a critical security bug fix is developed on 1 January 2020, the following new bug fix releases would need to be produced:

  • Jira 8.6.x because 8.6.0 was released on 17 December 2019
  • Jira 8.5.x because 8.5.0 was released on 21 October 2019
  • Jira 8.4.x because 8.4.0 was released on 9 September 2019
  • Jira 8.3.x because 8.3.0 was released on 22 July 2019
  • Jira 7.13.x because 7.13 is a Long Term Support release, and 7.13.0 was released on 28 November 2018

Confluence Server and Data Center

Issue new bug fix releases for:

  • Any versions designated a 'Long Term Support release' that have not reached end of life.
  • All feature versions released within 6 months of the date the fix is released.

For example, if a critical security bug fix is developed on 1 January 2020, the following new bug fix releases would need to be produced:

  • Confluence 7.2.x because 7.2.0 was released on 12 December 2019
  • Confluence 7.1.x because 7.1.0 was released on 4 November 2019
  • Confluence 7.0.x because 7.0.0 was released on 10 September 2019
  • Confluence 6.13.x because 6.13 is a Long Term Support release, and 6.13.0 was released on 4 December 2018

Bitbucket Server and Data Center

Issue new bug fix releases for:

  • Any versions designated a 'Long Term Support release' that have not reached end of life.
  • All feature versions released within 6 months of the date the fix is released.

For example, if a critical security bug fix is developed on 1 January 2020, the following new bug fix releases would need to be produced:

  • Bitbucket 6.9.x because 6.9.0 was released on 10 December 2019
  • Bitbucket 6.8.x because 6.8.0 was released on 6 November 2019
  • Bitbucket 6.7.x because 6.7.0 was released on 1 October 2019
  • Bitbucket 6.6.x because 6.6.0 was released on 27 August 2019
  • Bitbucket 6.5.x because 6.5.0 was released on 24 July 2019

Bitbucket 6.3.0 was released on 14 May 2019, more than 6 months before the date of the fix. If it was designated a Long Term Support release, a bug fix release would also be produced.

All other products (BambooCrucibleFisheye, etc)

We will only issue new bug fix releases for the current and previous feature release version.

For example, if a critical security bug fix is developed on 1 January 2020 for Bamboo, the following new bug fix releases would need to be produced:

  • Bamboo 6.10.x because it was released on 17 September 2019 and is the current release
  • Bamboo 6.9.x because 6.9.0 is the previous release

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:

Product

Example

Jira Software

Example

Jira Software 9.13.x because 9.13.0 is the latest feature release

Example

Jira Software 9.12.x because 9.12.0 is the latest Long Term Support release

Example

Jira Software 9.4.x because 9.4.0 is the previous Long Term Support release

Jira Service Management

Example

Jira Service Management 5.13.x because 5.13.0 is the latest feature release

Example

Jira Service Management 5.12.x because 5.12.0 is the latest Long Term Support release

Example

Jira Service Management 5.4.x because 5.4.0 is the second latest supported Long Term Support release

Confluence

Example

Confluence 8.7.x because 8.7.0 is the latest feature release

Example

Confluence 8.5.x because 8.5.0 is the latest Long Term Support release

Example

Confluence 7.19.x because 7.19.0 is the second latest supported Long Term Support release

Bitbucket

Example

Bitbucket 8.17.x because 8.17.0 is the latest feature release

Example

Bitbucket 8.9.x because 8.9.0 is the latest Long Term Support release

Example

Bitbucket 7.21.x because 7.21.0 is the second latest supported Long Term Support release

Bamboo

Example

Bamboo 9.5.x because 9.5.0 is the latest feature release

Example

Bamboo 9.2.x because 9.2.0 is the latest Long Term Support release

Crowd

Example

Crowd 5.3.x because 5.3.0 is the latest feature release

Fisheye/Crucible

Example

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.

Non-critical vulnerabilities

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.

You should upgrade your installations when a bug fix release becomes available to ensure that the latest security fixes have been applied.

Other information

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.

FAQ

What is a security bug fix? Copy link to heading Copied! Show +
  

A security bug fix is a set of changes made to a system or application to address vulnerabilities that could potentially be exploited by hackers. These vulnerabilities, also known as security bugs, could lead to unauthorized access, data theft, or other malicious activities.

What is vulnerability? Copy link to heading Copied! Show +
  

Vulnerability refers to a weakness or flaw that may be exploited by a threat or risk. In the context of cybersecurity, a vulnerability could be a flaw in software, network, or system that allows unauthorized users to gain access, cause damage. This could include things like outdated software, weak passwords, or missing data encryption.

Where can I find more information on fixed vulnerabilities in Data Center products? Copy link to heading Copied! Show +
  

Atlassian publishes monthly Security Advisories and provides access to the Vulnerability Disclosure Portal. The Vulnerability Disclosure Portal is a central hub for information about disclosed vulnerabilities in any of our products. It is updated monthly with the release of each Security Bulletin and provides an easy way to search and access data from previous bulletins.

What is a Long Term Support release? Copy link to heading Copied! Show +
  

Long Term Support releases are for Data Center customers who prefer to allow more time to prepare for upgrades to new feature versions but still need to receive bug fixes. Some products will designate a particular version to be a Long Term Support release, which means that security bug fixes will be made available for the full 2-year support window.

What is a Feature release? Copy link to heading Copied! Show +
  

A Feature release is a version (for example, Jira Software 9.11) that contains new features or major changes to existing features and that hasn't been designated a Long Term Support release. Learn more about the Atlassian Bug Fixing Policy.