Affected versions of Atlassian Jira Server and Data Center allow users who have watched an issue to continue receiving updates on the issue even after their Jira account is revoked, via a Broken Access Control vulnerability in the issue notification feature. The affected versions are before version 8.19.0.

According to its self-reported version number, the instance of Atlassian Jira hosted on the remote web server is affected by a broken access control vulnerability in the issue notification feature. An unauthenticated, remote attacker can exploit this issue to receive updates on a Jira issue they have watched even after their Jira account is revoked.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version   number.

According to its self-reported version number, the instance of Atlassian Jira hosted on the remote web server is prior to 8.19.0. It is, therefore, affected by multiple vulnerabilities:

- A broken access control vulnerability in the issue notification feature allowing users who have watched an issue to continue receiving updates on the issue even after their Jira account is revoked. (CVE-2021-39119)

- A denial of service (DoS) vulnerability in the GIF Image Reader component allowing remote attackers to impact the application's availability. (CVE-2021-39116) - A vulnerability that permits remote attackers to discover the usernames and full names of users via an enumeration vulnerability in the /rest/api/1.0/render endpoint.

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
157158	Atlassian Jira < 8.19.0 Broken Access Control (JRASERVER-72737)	Nessus	CGI abuses	Combined	medium
112960	Atlassian Jira < 8.19.0 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	Version Based	medium

Detections

Analytics

CVE-2021-39119

medium

Tenable Plugins

medium

medium