high
8.1
CWE
200
Advisory Published
CVE Published
Updated

CVE-2015-5152: Infoleak

First published: Wed Jul 15 2015(Updated: )

Dominic Cleal of Red Hat reports: The "require_ssl" setting (in /etc/foreman/settings.yml) should enforce that web requests sent to Foreman over HTTP are redirected to HTTPS, but this was found not to happen with API requests (e.g. from Hammer CLI). Foreman will process API requests over HTTP, but should have redirected. Redirection won't help with credentials having already been sent, but should give some notification that the user/app is using the wrong URL. Affects all versions of Foreman since 1.1. The issue has already been fixed since Foreman 1.9.0-RC1 via a refactor in #10471. To mitigate this with Apache, add a stanza to the HTTP VirtualHost (e.g. in /etc/httpd/conf.d/05-foreman.d/api_redirect.conf) similar to: RewriteEngine On RewriteRule ^/api/(.*) <a href="https://%{SERVER_NAME}/api/$1">https://%{SERVER_NAME}/api/$1</a> [R,L] External reference: <a href="http://projects.theforeman.org/issues/11119">http://projects.theforeman.org/issues/11119</a>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
The Foreman=1.1-1
The Foreman=1.2.0
The Foreman=1.2.0-rc1
The Foreman=1.2.0-rc2
The Foreman=1.2.0-rc3
The Foreman=1.2.1
The Foreman=1.2.2
The Foreman=1.2.3
The Foreman=1.3.0
The Foreman=1.3.0-rc1
The Foreman=1.3.0-rc2
The Foreman=1.3.0-rc3
The Foreman=1.3.0-rc4
The Foreman=1.3.1
The Foreman=1.3.2
The Foreman=1.4.0
The Foreman=1.4.0-rc1
The Foreman=1.4.0-rc2
The Foreman=1.4.1
The Foreman=1.4.2
The Foreman=1.4.3
The Foreman=1.4.4
The Foreman=1.4.5
The Foreman=1.5.0
The Foreman=1.5.1
The Foreman=1.5.2
The Foreman=1.5.3
The Foreman=1.6.0
The Foreman=1.6.0-rc1
The Foreman=1.6.0-rc2
The Foreman=1.6.1
The Foreman=1.7.0
The Foreman=1.7.0-rc1
The Foreman=1.7.0-rc2
The Foreman=1.7.1
The Foreman=1.7.2
The Foreman=1.7.3
The Foreman=1.7.4
The Foreman=1.7.5
The Foreman=1.8.0
The Foreman=1.8.0-rc1
The Foreman=1.8.0-rc2
The Foreman=1.8.0-rc3
The Foreman=1.8.1
The Foreman=1.8.2
The Foreman=1.8.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2015-5152?

    CVE-2015-5152 has a medium severity rating due to improper SSL enforcement on API requests.

  • How do I fix CVE-2015-5152?

    To fix CVE-2015-5152, ensure that the 'require_ssl' setting is correctly configured to enforce HTTPS for all API requests.

  • Which versions of Foreman are affected by CVE-2015-5152?

    CVE-2015-5152 affects Foreman versions 1.1-1 through 1.8.3.

  • What can happen if CVE-2015-5152 is exploited?

    If CVE-2015-5152 is exploited, it may allow sensitive data to be transmitted over unencrypted HTTP, exposing it to potential interception.

  • Is there a patch available for CVE-2015-5152?

    Yes, updates and patches addressing CVE-2015-5152 are available for affected versions of Foreman.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203