Security readout for executives and security teams
Plain-English summary
Ansible Tower 3.6.x before 3.6.2 could leave backup files readable by all local users. Those backups include the Tower SECRET_KEY and database backup, which can expose credentials stored in Tower.
Executive priority
Prioritize remediation for Tower instances managing production, cloud, or privileged automation credentials. The flaw is local-access only, but exposed backups can disclose every credential stored in Tower.
Technical view
CVE-2019-19341 is a CWE-732 file-permission flaw in Ansible Tower backups under /var/backup/tower. A low-privileged local user who can access the Tower server and knows backup timing may read sensitive backup content.
Likely exposure
Exposure is limited to Ansible Tower 3.6.x before 3.6.2, especially servers with multiple local users or broad shell access.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires local server access and awareness of backup timing, but impact is high confidentiality loss.
Researcher notes
CVSS 3.0 score is 5.9 with local attack vector, low privileges, user interaction required, changed scope, and high confidentiality impact. Evidence is limited to the CVE data and Red Hat Bugzilla reference in the bundle.
Mitigation direction
- Upgrade Ansible Tower 3.6.x deployments to 3.6.2 or later.
- Review Red Hat guidance for any product-specific remediation details.
- Restrict local shell access to Tower servers.
- Limit backup directory permissions to authorized administrative users only.
- Rotate credentials stored in Tower if backup exposure is suspected.
Validation and detection
- Inventory Tower versions and identify any 3.6.x deployments before 3.6.2.
- Check whether /var/backup/tower files are world-readable.
- Review local user accounts with access to Tower servers.
- Review access activity around scheduled Tower backup windows.
- Confirm exposed Tower-stored credentials were rotated where needed.
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.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-19341 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
- Medium
- CVSS
- 5.9 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N1.54Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
5.9MediumVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19341CVE reference · x_refsource_CONFIRM
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.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.