CVE-2019-15005· NVD / CVE Program· CNA atlassian

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

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 70.5% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.3 · v3.1—No exploit No fix recorded

Broken access control (IDOR)

Published: Nov 8, 2019
Updated: Jun 16, 2026
EPSS: 1.3% · 71th percentile
CWE: CWE-862

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
atlassian	troubleshooting and support	cpe:2.3:a:atlassian:troubleshooting_and_support
atlassian	bamboo	cpe:2.3:a:atlassian:bamboo
atlassian	bitbucket	cpe:2.3:a:atlassian:bitbucket
atlassian	confluence	cpe:2.3:a:atlassian:confluence
atlassian	crowd	cpe:2.3:a:atlassian:crowd
atlassian	crucible	cpe:2.3:a:atlassian:crucible
atlassian	fisheye	cpe:2.3:a:atlassian:fisheye
atlassian	jira	cpe:2.3:a:atlassian:jira

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

atlassian bamboobefore 6.10.2
atlassian bitbucketbefore 6.6.0
atlassian confluencebefore 7.0.1
atlassian crowdbefore 3.6.0
atlassian cruciblebefore 4.7.2
atlassian fisheyebefore 4.7.2
atlassian jirabefore 8.3.2
atlassian troubleshooting and supportbefore 1.17.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

Atlassian Bamboo
- unspecified and later · before 6.10.2affected
Atlassian Bitbucket Server
- unspecified and later · before 6.6.0affected
Atlassian Confluence Server
- unspecified and later · before 7.0.1affected
Atlassian Crowd
- unspecified and later · before 3.6.0affected
Atlassian Crucible
- unspecified and later · before 4.7.2affected
Atlassian Fisheye
- unspecified and later · before 4.7.2affected
Atlassian Jira Server
- unspecified and later · before 8.3.2affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope