Security readout for executives and security teams
Plain-English summary
This flaw lets a low-privileged Atlassian user trigger support log scans and send results to an email address they choose. Those emails may expose application configuration details. It affects several Atlassian Server/Data Center products when they include the vulnerable Troubleshooting and Support Tools plugin.
Executive priority
Treat as a moderate-priority internal exposure issue. It is not presented as remote unauthenticated code execution, but configuration leakage from collaboration and development systems can support later compromise.
Technical view
CVE-2019-15005 is a missing authorization check in Atlassian Troubleshooting and Support Tools before 1.17.2. An unprivileged authenticated user can initiate periodic log scans and direct results to arbitrary email. The issue is bundled in older Bitbucket, Confluence, Jira, Crowd, Fisheye, Crucible, and Bamboo releases.
Likely exposure
Exposure is most likely in self-managed Atlassian Server or Data Center deployments below the fixed product versions, or with the Troubleshooting and Support Tools plugin below 1.17.2. Internet exposure is not required if unprivileged internal users can authenticate.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, CVSS, or exploit maturity. The described attacker is an unprivileged authenticated user. Impact is information disclosure through emailed log-scan results, potentially including application configuration information.
Researcher notes
Key unknowns are CVSS score, exact endpoint behavior, and product-specific UI/API paths. Avoid assuming broader data access than configuration information in emailed log-scan results unless confirmed in the target environment.
Mitigation direction
- Upgrade the Troubleshooting and Support Tools plugin to version 1.17.2 or later.
- Upgrade affected Atlassian products to the fixed versions listed in the CVE description.
- Check Atlassian advisories for product-specific remediation guidance.
- Review whether exposed configuration data requires credential or secret rotation.
Validation and detection
- Inventory affected Atlassian Server and Data Center products and versions.
- Check the installed Troubleshooting and Support Tools plugin version.
- Review whether non-admin users can access log-scan scheduling features.
- Look for unexpected periodic log scans or support emails to unusual recipients.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-15005 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/BAM-20647CVE reference · x_refsource_MISC
- https://herolab.usd.de/security-advisories/usd-2019-0016/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.