Bug 2244213 - sos: Ansible Automation Platform collects customer passwords and tokens via sosreport
Summary: sos: Ansible Automation Platform collects customer passwords and tokens via s...
Keywords:
Status: NEW
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2244214
Blocks: 2244215
TreeView+ depends on / blocked
 
Reported: 2023-10-14 16:54 UTC by Nick Tait
Modified: 2024-02-07 13:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Nick Tait 2023-10-14 16:54:24 UTC
When working with customer cases many Red Hat support employees regularly make use of a tool called "SOS report" [1]. This tool gathers various files that may be of interest to the supporter working a specific case to troubleshoot a customer issue.

Developers of this tool aim to obfuscate/remove all secrets, passwords and tokens that are present in these files. Unfortunately, we have been gathering the passwords of customers that are running Ansible Automation Platform on RHEL (possibly OpenShift too) for quite a while now.

The list of known erroneously gathered passwords/tokens/secrets are below. There may be others that have not yet been identified.
- Database password
- LDAP bind password
- Broadcast secret (Ansible Automation Platform specific)
- Email password (if notifications are enabled within the Ansible Automation Platform)

A fix is already in place upstream for both the Ansible Automation Platform Controller [2] and Ansible Automation Hub [3], which are both components of the Ansible Automation Platform.

[1]: https://access.redhat.com/solutions/3592
[2]: https://github.com/ansible/awx/pull/14557
[3]: https://github.com/sosreport/sos/pull/3379

Comment 1 Nick Tait 2023-10-14 16:56:07 UTC
Created sos tracking bugs for this issue:

Affects: fedora-all [bug 2244214]


Note You need to log in before you can comment on or make changes to this bug.