Skip to content
Fencer Intel
medium 4.3

CVE-2019-15005 json

The Atlassian Troubleshooting and Support Tools plugin prior to version 1.17.2 allows an unprivileged user to initiate periodic log scans a…

published 7y ago modified 4mo ago also EUVD-2019-6092

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

The Atlassian Troubleshooting and Support Tools plugin prior to version 1.17.2 allows an unprivileged user to initiate periodic log scans and send the results to a user-specified email address due to a missing authorization check. The email message may contain configuration information about the application that the plugin is installed into. A vulnerable version of the plugin is included with Bitbucket Server / Data Center before 6.6.0, Confluence Server / Data Center before 7.0.1, Jira Server / Data Center before 8.3.2, Crowd / Crowd Data Center before 3.6.0, Fisheye before 4.7.2, Crucible before 4.7.2, and Bamboo before 6.10.2.

Patch / fix

  • Atlassian Bitbucket Server 6.6.0
  • Atlassian Jira Server 8.3.2
  • Atlassian Confluence Server 7.0.1
  • Atlassian Crowd 3.6.0
  • Atlassian Fisheye 4.7.2
  • Atlassian Crucible 4.7.2
  • Atlassian Bamboo 6.10.2

Is CVE-2019-15005 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

  • Atlassian Bitbucket Server
  • Atlassian Jira Server
  • Atlassian Confluence Server
  • Atlassian Crowd
  • Atlassian Fisheye
  • Atlassian Crucible
  • Atlassian Bamboo

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.