CVE-2015-5233: Medium severity the foreman vulnerability

Published Sep 11, 2015
·
Updated

Dominic Cleal of the Red Hat Satellite Team reports:

Reports (from tools such as Puppet) are stored in Foreman and associated to the host they came from. Users can be granted permissions to view and/or destroy reports, and also separate permissions to view certain hosts. The UI and API only list reports where the user has permission to view both reports and the host it was from.

The security issue is that both the show and destroy actions for viewing and deleting individual reports do not limit access to the hosts that the user has permission to view. A user with permission to view or destroy reports can do so for any host if they know the ID, or can easily view the last report for a given host.

External Reference: http://projects.theforeman.org/issues/11579

Other sources

Foreman before 1.8.4 and 1.9.x before 1.9.1 do not properly apply viewhosts permissions, which allows (1) remote authenticated users with the viewreports permission to read reports from arbitrary hosts or (2) remote authenticated users with the destroyreports permission to delete reports from arbitrary hosts via direct access to the (a) individual report show/delete pages or (b) APIs.

MITRE

Affected Software

3 affected components
theforeman foreman<=1.8.3
theforeman foreman=1.9.0
redhat Satellite=6.1

Event History

Sep 11, 2015
Data Sourced
via Red Hat·05:04 PM
DescriptionSeverityAffected Software
Apr 11, 2016
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2015-5233?

CVE-2015-5233 has a medium severity rating due to improper permission handling allowing unauthorized access to reports.

2

How do I fix CVE-2015-5233?

To fix CVE-2015-5233, upgrade Foreman to version 1.8.4 or later, or 1.9.1 or later.

3

Who is affected by CVE-2015-5233?

CVE-2015-5233 affects users of Foreman versions before 1.8.4 and 1.9.0, as well as Red Hat Satellite 6.1.

4

What are the risks of CVE-2015-5233?

The risks of CVE-2015-5233 include unauthorized users being able to read or delete sensitive reports from other hosts.

5

Is there a workaround for CVE-2015-5233?

There is no official workaround for CVE-2015-5233, and the only solution is to update to the fixed versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203