Katello has a Denial of Service vulnerability in API OAuth authentication
A cleartext password storage issue was discovered in Katello, versions 3.x.x.x before katello 3.12.0.9. Registry credentials used during container image discovery were inadvertently logged without being masked. This flaw could expose the registry credentials to other privileged users.
A cross-site scripting (XSS) flaw was found in the katello component of Satellite. An attacker with privilege to create/edit organizations and locations is able to execute a XSS attacks against other users through the Subscriptions or the Red Hat Repositories wizards. This can possibly lead to malicious code execution and extraction of the anti-CSRF token of higher privileged users. Versions before 3.9.0 are vulnerable.
A SQL injection flaw was found in katello's errata-related API. An authenticated remote attacker can craft input data to force a malformed SQL query to the backend database, which will leak internal IDs. This is issue is related to an incomplete fix for CVE-2016-3072. Version 3.10 and older is vulnerable.
A flaw was found in Foreman's katello plugin version 3.4.5. After setting a new role to allow restricted access on a repository with a filter (filter set on the Product Name), the filter is not respected when the actions are done via hammer using the repository id.
A flaw was found in katello-debug before 3.4.0 where certain scripts and log files used insecure temporary files. A local user could exploit this flaw to conduct a symbolic-link attack, allowing them to overwrite the contents of arbitrary files.
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the updateroles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.
Eric Helms (ehelms) reports:
I have identified a number of areas and entities within Katello that are vulnerable to a cross-site scripting attack.
Reproducible: Always
Steps to Reproduce: 1. Log in 2. Navigate to Changeset/Repository/System/Distributor/Filter 3. Create a new entity from above giving it the name <a href="http://www.google.com">Entity 1</a> 4. Submit Actual Results: - Notification pops up saying success with a clickable link - Users can navigate to 'Notices' page and see clickable link from successful creation of the entity - If creating a Changeset, the changeset name will appear clickable inside the right hand list on the Changeset Management page
Expected Results: The name should appear fully escaped everywhere that it is used.
This is a two fold issue:
1. This issue is not present with some entities due to model validation on the backend that prevents the use of HTML <,>,/ characters. The entities defined above in the steps do not have this validation on their name property.
2. There are a few places where user input is not escaped on output. These locations are: - notices displayed to the user are marked as htmlsafe to account for the application putting links for the user into some notices, this has the downside of presenting all notices unescaped to the user and opening this XSS hole - in some areas of the application, JavaScript is used to construct templates and concatenate user input data from the server, since this data is not escaped when input to the JavaScript, the result comes out with an XSS hole
The installation script in Katello 1.0 and earlier does not properly generate the Application.config.secrettoken value, which causes each default installation to have the same secret token, and allows remote attackers to authenticate to the CloudForms System Engine web interface as an arbitrary user by creating a cookie using the default secrettoken.