319 advisories tracked · Atlassian (security@atlassian.com CNA) via NVD · checked automatically every minute
Pick your product and enter the exact software release it runs. We match it against the affected/fixed versions in Atlassian's recent advisories.
Atlassian (security@atlassian.com CNA) via NVD
Atlassian is its own CVE Numbering Authority. VulniPulse ingests Atlassian's CVEs from the NVD CNA feed (security@atlassian.com), each linking to its security advisory / Jira ticket. Covers Confluence (Server & Data Center), Jira (Software & Service Management), Bitbucket, Bamboo, Crowd and Fisheye/Crucible — self-hosted Confluence/Jira are repeatedly hit by mass-exploited RCE and auth-bypass bugs (CVE-2023-22515, CVE-2022-26134), so a huge patch-now audience.
Visit Atlassian security advisoriesThis Critical severity OS Command Injection vulnerability was introduced in versions 9.6.0, 10.0.0, 10.1.0, 10.2.0, 11.0.0, 11.1.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 9.4 and a CVSS Vector of CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H allows an authenticated attacker to execute commands on the remote system, which has high impact to confidentiality, high 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 9.6.0: Upgrade to a release greater than or equal to 9.6.25 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]).
This High severity RCE (Remote Code Execution) vulnerability was introduced in versions 9.6.0, 10.0.0, 10.1.0, 10.2.0, 11.0.0, 11.1.0, 12.0.0, and 12.1.0 of Bamboo Data Center. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8.6, allows an authenticated attacker to execute malicious code on the remote system. 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 9.6: Upgrade to a release greater than or equal to 9.6.24 Bamboo Data Center 10.2: Upgrade to a release greater than or equal to 10.2.16 Bamboo Data Center 12.1: Upgrade to a release greater than or equal to 12.1.3 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]). This vulnerability was reported via our Atlassian (Internal) program.
This High severity XXE (XML External Entity Injection) vulnerability was introduced in version 7.1.0 of Crowd Data Center and Server. This XXE (XML External Entity Injection) vulnerability, with a CVSS Score of 7.9, allows an authenticated attacker to access local and remote content which has high impact to confidentiality, low impact to integrity, high impact to availability, and requires no user interaction. Atlassian recommends that Crowd Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Crowd Data Center and Server 7.1: Upgrade to a release greater than or equal to 7.1.3 See the release notes (https://confluence.atlassian.com/crowd/crowd-release-notes-199094.html). You can download the latest version of Crowd Data Center and Server from the download center (https://www.atlassian.com/software/crowd/download-archive). This vulnerability was reported via our Atlassian (Internal) program.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Rejected reason: To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view items on the "Why" page.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view other team overviews.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view audit log items.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to modify the steps of another user's private checklist.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view portfolio rooms without the required permission.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to view certain sprint data without the required permission.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to read external reports without the required permission.
Jira Align is vulnerable to an authorization issue. A low-privilege user is able to alter the private checklists of other users.
Jira Align is vulnerable to an authorization issue. A low-privilege user without sufficient privileges to perform an action could if they included a particular state-related parameter of a user with sufficient privileges to perform the action.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to subscribe to an item/object without having the expected permission level.
Jira Align is vulnerable to an authorization issue. A low-privilege user can access unexpected endpoints that disclose a small amount of sensitive information. For example, a low-level user was able to read the steps of another user's private checklist.