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.

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.

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.

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.

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.

Vulnerability/
CVE-2015-5233

medium

CWE

264

11/9/2015

11/4/2016

6/8/2024

CVE-2015-5233

First published: Fri Sep 11 2015(Updated: )

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

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
TheForeman Foreman	<=1.8.3
TheForeman Foreman	=1.9.0
redhat satellite	=6.1

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
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.

agent/type
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2015-5233
agent/first-publish-date
agent/author
agent/weakness
agent/references
agent/severity
agent/remedy
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/theforeman
canonical/theforeman foreman
version/theforeman foreman/1.8.3
version/theforeman foreman/1.9.0
vendor/redhat
canonical/redhat satellite
version/redhat satellite/6.1

Company

Resources

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.

Frequently Asked Questions

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.
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.
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.
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.
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.