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 Software | Affected Version | How to fix |
---|---|---|
TheForeman Foreman | =1.1-1 | |
TheForeman Foreman | =1.2.0 | |
TheForeman Foreman | =1.2.0-rc1 | |
TheForeman Foreman | =1.2.0-rc2 | |
TheForeman Foreman | =1.2.0-rc3 | |
TheForeman Foreman | =1.2.1 | |
TheForeman Foreman | =1.2.2 | |
TheForeman Foreman | =1.2.3 | |
TheForeman Foreman | =1.3.0 | |
TheForeman Foreman | =1.3.0-rc1 | |
TheForeman Foreman | =1.3.0-rc2 | |
TheForeman Foreman | =1.3.0-rc3 | |
TheForeman Foreman | =1.3.0-rc4 | |
TheForeman Foreman | =1.3.1 | |
TheForeman Foreman | =1.3.2 | |
TheForeman Foreman | =1.4.0 | |
TheForeman Foreman | =1.4.0-rc1 | |
TheForeman Foreman | =1.4.0-rc2 | |
TheForeman Foreman | =1.4.1 | |
TheForeman Foreman | =1.4.2 | |
TheForeman Foreman | =1.4.3 | |
TheForeman Foreman | =1.4.4 | |
TheForeman Foreman | =1.4.5 | |
TheForeman Foreman | =1.5.0 | |
TheForeman Foreman | =1.5.1 | |
TheForeman Foreman | =1.5.2 | |
TheForeman Foreman | =1.5.3 | |
TheForeman Foreman | =1.6.0 | |
TheForeman Foreman | =1.6.0-rc1 | |
TheForeman Foreman | =1.6.0-rc2 | |
TheForeman Foreman | =1.6.1 | |
TheForeman Foreman | =1.7.0 | |
TheForeman Foreman | =1.7.0-rc1 | |
TheForeman Foreman | =1.7.0-rc2 | |
TheForeman Foreman | =1.7.1 | |
TheForeman Foreman | =1.7.2 | |
TheForeman Foreman | =1.7.3 | |
TheForeman Foreman | =1.7.4 | |
TheForeman Foreman | =1.7.5 | |
TheForeman Foreman | =1.8.0 | |
TheForeman Foreman | =1.8.0-rc1 | |
TheForeman Foreman | =1.8.0-rc2 | |
TheForeman Foreman | =1.8.0-rc3 | |
TheForeman Foreman | =1.8.1 | |
TheForeman Foreman | =1.8.2 | |
TheForeman Foreman | =1.8.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5152 has a medium severity rating due to improper SSL enforcement on API requests.
To fix CVE-2015-5152, ensure that the 'require_ssl' setting is correctly configured to enforce HTTPS for all API requests.
CVE-2015-5152 affects Foreman versions 1.1-1 through 1.8.3.
If CVE-2015-5152 is exploited, it may allow sensitive data to be transmitted over unencrypted HTTP, exposing it to potential interception.
Yes, updates and patches addressing CVE-2015-5152 are available for affected versions of Foreman.