CVE-2015-5152: Infoleak
Dominic Cleal of Red Hat reports:
The "requiressl" 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/apiredirect.conf) similar to:
RewriteEngine On RewriteRule ^/api/(.) https://%{SERVERNAME}/api/$1 [R,L]
External reference:
http://projects.theforeman.org/issues/11119
Other sources
Foreman after 1.1 and before 1.9.0-RC1 does not redirect HTTP requests to HTTPS when the requiressl setting is set to true, which allows remote attackers to obtain user credentials via a man-in-the-middle attack.
— MITRE
Affected Software
Event History
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.