We take security issues seriously and welcome responsible disclosure from researchers discovering vulnerabilities in Foreman. Please email foreman-security@googlegroups.com (a private address for the security team) with all reports. If you notice the security issue is related to a particular plugin, please mention the plugin within the body of the email to help us in routing the issue to the most authoritative source.

We will endeavour to resolve high severity issues in the current stable release and lower severity issues in the next major release. Announcements of security issues will be made on this page and in the Release Announcements category of our community forums when a release containing a fix is available to end users and credit will be given to the researcher if desired.

The policy of the project is to treat all newly reported issues as private, and after evaluation, low to medium severity issues will be made public while high severity issues will be fixed under an embargo. Typically the project supports only one major (x.y) release at a time, though high severity issues may also be fixed in the previous release if it was only recently superseded.

All security advisories made for Foreman are listed below with their corresponding CVE identifier.

• CVE-2023-4886: World readable tomcat server.xml contains passwords
• CVE-2022-4130: Blind SSRF via Referer header
• CVE-2022-3874: OS command injection via ct_command and fcct_command
• CVE-2021-3584: Remote code execution through Sendmail configuration
• CVE-2021-20256: BMC controller credential leak via API
• CVE-2021-20259: Proxmox compute resource password leak
• CVE-2021-3413: Azure compute resource secret_key leak
• CVE-2020-14335: World readable dhcp OMAPI secret
• CVE-2020-14380: Users can gain elevated rights when logging in with SSO accounts
• CVE-2020-14334: World readable cache directory on RPM installs
• CVE-2019-14825: Registry credentials are captured in plain text in dynflow task during repository discovery
• CVE-2019-10198: Information disclosure in foreman tasks plugin
• CVE-2019-3845: Lack of access control around Qpid message broker
• CVE-2019-3893: Compute resource credentials exposed during deletion on API
• CVE-2018-14664: Persisted XSS on all pages that use breadcrumbs
• CVE-2018-1097: oVirt credetials exposed by power API
• CVE-2018-1096: SQL injection on dashboard
• CVE-2017-15100: Stored XSS in fact charts
• CVE-2017-7535: Stored XSS when assigning unassigned hosts to organization/location
• CVE-2017-7505: User scoped in organization with permissions for user management can manage administrators that are not assigned to any organization
• CVE-2017-2672: audit log stores plain text compute resource image passwords
• CVE-2017-2667: Hammer CLI does not verify server SSL certificate
• CVE-2016-9593: foreman-debug collects sensitive data
• CVE-2016-8639: settings dropdown menus may run stored XSS in org/location name
• CVE-2016-8634: organizations/locations wizard may run stored XSS in name
• CVE-2016-7078: user with no organizations or locations can see all resources
• CVE-2016-7077: information disclosure from association lists shown without authorization
• CVE-2016-6320: network interface device identifiers may contain stored XSS on host form
• CVE-2016-6319: Foreman form helpers do not escape JS when rendering label
• CVE-2016-5390: API host interfaces data not restricted by view_hosts filters
• CVE-2016-4995: information disclosure through unauthorized template previews
• CVE-2016-4475: Privilege escalation in Organization and Locations API and UI
• CVE-2016-4451: Privilege escalation through Organization and Locations API
• CVE-2016-3728: remote code execution in smart proxy TFTP API
• CVE-2016-3693: application information leakage through templates
• Ruby code execution via Discovery settings
• CVE-2016-2100: private bookmarks can be viewed and edited
• CVE-2015-7518: parameter information popup allows stored XSS
• SQL injection via facts search terms
• CVE-2015-5282: parameter hide checkbox allows stored XSS during change
• CVE-2015-5246: Active Directory login works with old password after change
• CVE-2015-5233: reports show/destroy not restricted by host authorization
• CVE-2015-5152: require_ssl does not enforce HTTPS on API
• CVE-2015-3235: edit_users permission allows changing of admin passwords
• CVE-2015-3199: Discovery: auto provision rule not enforcing org/locations
• CVE-2015-3155: session cookie set without secure flag on HTTPS
• CVE-2015-1844: users are not restricted to organizations/locations
• CVE-2015-1816: SSL certificate not verified on LDAP connections
• CVE-2014-3691: SSL certificate verification bypass in smart proxy
• CVE-2014-3653: stored cross site scripting (XSS) in template previews
• CVE-2014-3590: user logout vulnerable to CSRF
• CVE-2014-3531: stored cross site scripting (XSS) in operating system names
• CVE-2014-3492: stored cross site scripting (XSS) in YAML preview
• CVE-2014-3491: stored cross site scripting (XSS) in notification dialogs
• CVE-2014-0007: TFTP boot file fetch API permits remote code execution
• CVE-2014-0208: stored cross site scripting (XSS) in search auto-completion
• CVE-2014-0192: provisioning template previews are world-readable
• CVE-2014-0135: Kafo leaves world-readable default_values.yaml file
• CVE-2014-0090: session fixation, new session IDs are not generated on login
• CVE-2014-0089: stored cross site scripting (XSS) on 500 error page
• CVE-2013-4386: SQL injection in host/host group parameter overrides
• CVE-2013-4182: hosts API privilege escalation
• CVE-2013-4180: DoS via hosts controller input conversion
• CVE-2013-2121: bookmarks remote code execution
• CVE-2013-2113: admin user creation, privilege escalation
• CVE-2013-0210: Arbitrary command execution risk in Foreman proxy
• CVE-2013-0187: XMLHttpRequest bypasses authorization
• CVE-2013-0174: exposed hashed root passwords can be retrieved by unauthenticated remote users
• CVE-2013-0173: insecure fixed salt "foreman" for passwords
• CVE-2013-0171: import allows unauthenticated YAML uploads/parsing leading to arbitrary code execution
• CVE-2012-5648: SQL injection through search mechanism
• CVE-2012-5477: world writable files in proxy

The world readable file /etc/tomcat/server.xml contains passwords for the keystore and truststore. The actual stores are limited by file permissions, but server.xml should also be limited.

• Affects Katello
• Fix released in Foreman 3.8.0
• Redmine issue #36760

A blind site-to-site request forgery vulnerability was found in Satellite server. It is possible to trigger an external interaction to an attacker's server by modifying the Referer header in an HTTP request of specific resources in the server.

• Affects Foreman
• Fix released in Foreman 3.8.0
• Redmine issue #36768

ct_command and fcct_command settings, available via Administer - Settings, both accept arbitrary strings as the command name and calling CoreOS templates will execute those commands as the user Foreman runs under. By default, only Foreman super administrator can access settings.

• Affects Foreman 3.2.0 and higher
• Fix released in Foreman 3.8.0
• Redmine issue #36759

Sendmail location and arguments, available via Administer - Settings, both accept arbitrary strings and pass them into shell. By default, only Foreman super administrator can access settings.

• Affects Foreman 1.15.0 and higher
• Fix released in Foreman 2.4.1, 2.5.1 and 3.0.0
• Redmine issue #32753

A password leak was identified on Foreman which will expose BMC password in plaintext through the host API.

• Affects Foreman 1.4.0 and higher
• Fix released in Foreman 2.5.0
• Redmine issue #31937

Proxmox compute resource credentials (password) were visible to any user with view_compute_resource permission in the API under /api/compute_resources/ and /api/compute_resources/:id/.

• Affects Foreman Fog Proxmox 0.11.0 and higher
• Fix released in Foreman Fog Proxmox 0.13.1 and higher

Azure compute resource credentials (secret_key) were visible to any user with view_compute_resource permission in the API under /api/compute_resources/ and /api/compute_resources/:id/.

• Affects Foreman Azure RM 2.0.1 and higher
• Fix released in Foreman Azure RM 2.2.0 and higher
• Redmine issue #31938

OMAPI key used to secure dhcp API access could have been read by anyone with access to the hosting system.

Mitigation: override /etc/dhcp/dhcpd.conf file mode to 0640 and ensure access to the file for user foreman-proxy by other means.

On Red Hat based systems, acls are used by default, so you need to only set less permissive mode and you should be set. On Debian based systems, you need to install acls and set read access to the /etc/dhcp directory by acls. To set correct acls install acl package and use setfacl -R -m u:foreman-proxy:rx /etc/dhcp.

In case the system may have been accessed locally by an un-trusted user, it may be prudent to change the OMAPI secret for dhcp.

• Affects foreman-proxy installations with dhcp feature protected by dhcp_key_secret since Foreman 1.0
• Fix released in Foreman 2.2.0 and 2.1.3 and higher
• Redmine issue #30489

Users that are authenticated using external authentication methods such as Kerberos, OpenID Connect or Apache SSO can gain the rights of an internal user. This is possible only when the username of an internal and external user is the same.

• Affects external user authentication since Foreman 1.4
• Fix released in Foreman 2.2.0, 2.1.3 and 2.0.3 and higher
• Redmine issue #30739

Even encrypted settings have their raw values cached. Too permissive mode on cache dir caused, that anyone with access to the hosting system could read this encrypted settings.

Mitigation: override /run/foreman directory mode to 0750. To do so in a manner that survives reboot, update the file /usr/lib/tmpfiles.d/foreman.conf.

d /run/foreman 0750 foreman foreman -

For the change to have effect immediatelly run systemd-tmpfiles --create.

In case the system may have been accessed locally by an un-trusted user, it may be prudent to change any secrets stored in the settings, such as OAuth keys or remote execution passwords.

• Affects RPM installations using file cache since Foreman 1.3
• Fix released in Foreman 2.2.0, 2.1.1 and 2.0.2 and higher
• Redmine issue #30490

A cleartext password storage issue was discovered in Katello. Registry credentials used during container image discovery were inadvertently logged without being masked. This could expose the registry credentials to other privileged users.

• Affects Katello 3.4 and higher.
• Fix released in Katello 3.14.0 and higher.
• Redmine issue #27485

The Foreman tasks plugin allowed authenticated users to view task details even if they lack the permission to do so. This bypass requires prior knowledge of the task UUID, which can not be easily guessed.

• Affects Foreman tasks 0.7.8 and higher.
• Fix released in Foreman tasks 0.15.7 and higher.
• Redmine issue #27275

Katello installations include the Apache Qpid message broker and dispatch router services. It was found that due to the lack of access permissions around the message broker and router, clients using the katello-agent for package management could invoke QMF (QPid Management Framework) actions against the broker. QMF enables broker settings, queues, exchanges, etc. to be manipulated and those actions could compromise communication between hosts and the server, or allow undesired katello-agent actions to be invoked across clients. This issue was reported by Pavel Moravec.

• Affects Katello 1.4 and higher.
• Fix released with Foreman 1.20.3 (Katello 3.10.1), Foreman 1.21.3 (Katello 3.11.1) and higher.
• Redmine issue #26571

When deleting a compute resource via the API, the API responded with details of the compute resource, including credentials in clear text. Users not able to upgrade should ensure the delete_compute_resource permission is not granted to users not trusted with the credentials.

• Affects Foreman 1.1 and higher.
• Fix released with Foreman 1.21.1.
• Redmine issue #26450

If user has the permission to edit resource which attribute is user in the breadcrumbs bar, it's not properly escaped allowing attacker to store code, that will be executed on client side. E.g. create a domain with name test.com, the go to it's edit form. See the breadcrumb didn't escape the HTML code.

• Affects Foreman 1.18 and higher
• Fix released with Foreman 1.18.3
• Redmine issue #25169

When sending a power action to a host provisioned on an oVirt compute resource, the API responded with details of the compute resource, including credentials in clear text.

• Affects Foreman 1.3 and higher.
• Fix released with Foreman 1.16.1.
• Redmine issue #22546

One of the parameters passed when saving dashboard widget positions was not properly escaped, leading to possibility of SQL injection attack. Due to the nature of the query the impact is limited to possible information disclosure and does not allow modifications to the database.

This issue was reported by Martin Povolný of Red Hat.

• Affects Foreman 1.9 and higher.
• Fix released with Foreman 1.16.1.
• Redmine issue #23028

Facts reported by hosts that contain HTML code in their fact name or value could cause said HTML to be executed by users' browser when hovering over fact distribution charts on the facts page, on the statistic page and on the trends page.

This issue was reported by Roman Mueller.

• Affects Foreman 1.2 and higher.
• Fix released with Foreman 1.16.0
• Redmine issue #21519

An organization or location named e.g. <script>do_evil();</script> may cause the script to be executed if a user tries to assign selected or all unassigned hosts to said organization or location.

This issue was reported by Sanket Jagtap.

• Affects Foreman 1.1 and higher.
• Fix released with Foreman 1.16.0
• Redmine issue #20963

User with *_users permissions who is assigned to some organization(s) can do all operations granted by these permissions on all administrator user objects. We considered admin to effectively be present in all organizations.

The issue was reported by David Caplan.

• Affects Foreman 1.5 and higher
• Fix released with Foreman 1.15.1
• Redmine issue #19612

Compute resource images added/registered in Foreman with username and password credentials will have the password stored in plain text in the audit log. A user with permission to view the audit log can view the password and may gain access to newly provisioned hosts.

This issue was reported by Daniel Kimsey.

• Affects Foreman 1.4 and higher
• Fix released with Foreman 1.15.0-RC2
• Redmine issue #19169

HTTPS connections initiated by Hammer CLI to the API server do not perform validation of the server SSL/TLS certificate, allowing for a man-in-the-middle attack against the user.

This issue was reported by Tomas Strachota.

• Affects all versions of Hammer CLI
• Fix released in Hammer CLI 0.10.0 (with Foreman 1.15.0)
• Redmine issue #19033

It was found that foreman-debug did not obfuscate sensitive information (such as passwords, answer and configuration options) from the foreman-installer log file, allowing a user authorized to access the archives created by foreman-debug to gain access to potentially sensitive information.

This issue was reported by Pavel Moravec.

• Affects Foreman 1.2.0 up to and including 1.14.x
• Fix released with Foreman 1.15.0-RC1
• Redmine issue #17005

If an organization or location is created with a name containing HTML, then the administrator-only Settings page will render the HTML as part of a dropdown menu.

This may permit a stored XSS attack if an organization/location with HTML in the name is created, then an administrator attempts to change the default organization/location settings.

Mitigation: restrict permissions to organization and location creation, use the API or CLI instead to change the default organization/location settings.

Note: this CVE identifier has been assigned retrospectively, to describe a vulnerability that was fixed during a refactoring of the affected code.

This issue was reported by Sanket Jagtap.

• Affects Foreman 1.11.0 to 1.12.4
• Fix released in Foreman 1.13.0
• Redmine issue #15037

When creating an organization or location in Foreman, if the name contains HTML then the second step of the wizard will render the HTML. This occurs in the alert box on the page.

This may permit a stored XSS attack if an organization/location with HTML in the name is created, then a user is linked directly to this URL.

Mitigation: restrict permissions to organization and location creation, don't follow untrusted links to Foreman.

This issue was reported by Sanket Jagtap.

• Affects Foreman 1.1 and higher
• Fix released in Foreman 1.14.0-RC1
• Redmine issue #17195

A user account that is associated to no organizations or locations is able to view resources from all organizations/locations in the web UI or API, when either the organization or location feature is enabled. The user remains subject to permissions and filters on their assigned roles.

Mitigation: ensure all users are assigned to at least one organization or location, or disable the feature if unused.

This issue was reported by Daniel Lobato Garcia.

• Affects all known Foreman versions
• Fix released in Foreman 1.15.0-RC1
• Redmine issue #16982

Lists of associated resources, such as operating systems associated to a new architecture, are not restricted to listing resources that the user is authorized to view, when rendering with fewer than six items. The list will show all possible associated resources, disclosing their names.

This issue was reported by Jitendra Yejare.

• Affects Foreman 1.1 and higher, but was first mitigated against in Foreman 1.9.0 for some cases
• Fix released in Foreman 1.14.0-RC1
• Redmine issue #16971

Network interface identifiers stored for hosts may contain HTML or JavaScript that allows a stored XSS (cross-site scripting) vulnerability when later viewing the host edit form.

This issue was reported by Sanket Jagtap.

• Affects Foreman 1.8.0 and higher
• Fix released in Foreman 1.12.2
• Redmine issue #16022

Label parameter of all form helpers was not escaped allowing XSS (cross-site scripting). The Foreman itself did not contain exploitable code but other plugins that relied on form helpers could be vulnerable. One known vulnerable plugin is Remote Execution. All versions of this plugin are affected.

• Affects Foreman 1.6.0 and higher
• Fix released in Foreman 1.12.2
• Redmine issue #16024

Non-admin users with the view_hosts permission containing a filter are able to access API routes beneath "hosts" such as GET /api/v2/hosts/secrethost/interfaces without the filter being taken into account. This allows users to access network interface details (including BMC login details) for any host.

The filter is only correctly used when accessing the main host details (/api/v2/hosts/secrethost). Access to the "nested" routes, which includes interfaces, reports, parameters, audits, facts and Puppet classes, is not authorized beyond requiring any view_hosts permission.

• Affects Foreman 1.10.0 and higher
• Fix released in Foreman 1.12.1 and 1.11.4
• Redmine issue #15653

Users who are logged in with permissions to view some hosts are able to preview provisioning templates for any host by specifying its hostname in the URL, as the specific view_hosts permissions and filters aren't checked.

If the organization or location features are enabled, the user will still be restricted to their associated orgs/locs.

• Affects Foreman 1.11.0 and higher
• Fix released in Foreman 1.12.1 and 1.11.4
• Redmine issue #15490

When accessing Foreman as a user limited to specific organization or location, these are not taken into account in the API or parts of the UI. This allows a user to view, edit and delete organizations and locations they are not associated with if they have the requisite permissions.

Mitigation: make sure you have filters restricted to organizations or locations when you limit user by assigning them to particular organizations or locations.

• Affects Foreman 1.1 and higher
• Fix released in Foreman 1.12.0-RC3 and 1.11.4
• Redmine issue #15268

When accessing Foreman as a user limited to specific organization, if users know other organization id and have unlimited filters they can access/modify other organization data. They just have to set the id as API parameter.

Mitigation: make sure you have filters restricted to organizations or locations when you limit user by assigning him particular organization or location.

• Affects Foreman 1.7 and higher
• Fix released in Foreman 1.12.0-RC1 and 1.11.3
• Redmine issue #15812

The smart proxy TFTP API is vulnerable to arbitrary remote code execution, as it passes untrusted user input (the PXE template type) to the eval() function causing it to be executed.

Thanks to Lukas Zapletal for reporting the issue.

Mitigation: ensure trusted_hosts is set in /etc/foreman-proxy/settings.yml, HTTPS is in use and /etc/foreman-proxy/settings.d/tftp.yml is configured for https only (if enabled).

• Affects Foreman 0.2 and higher
• Fix released in Foreman 1.11.2 and 1.10.4
• Redmine issue #14931

A provisioning template containing inspect will expose sensitive information about the Rails controller and application when rendered when using Safemode rendering (the default setting). This includes the application secret token, possibly permitting a privilege escalation.

Thanks to Ivan Necas for reporting the issue.

As a precaution, the security token may be regenerated with:

1. chown foreman /usr/share/foreman/config/initializers/local_secret_token.rb
2. foreman-rake security:generate_token
3. chown root /usr/share/foreman/config/initializers/local_secret_token.rb

Mitigation: remove edit_provisioning_templates from untrusted users.

• Affects all known Foreman versions
• Fix released in Foreman 1.11.1
• Redmine issue #14635

It is possible to run arbitrary Ruby code entering it on the Administer - Settings - Discovery and then visiting a discovered host detail page where it gets rendered.

• Affects Foreman Discovery 4.2.0 to 5.0.1 (gem releases only, rc and nightly builds)
• Discovery plugin 4.1 series (shipped with Foreman 1.10) was not affected.
• Fixed in Discovery plugin 5.0.2
• Redmine issue #14140

Bookmarks set to 'private' can be viewed by any user, and edited or deleted by any user granted the edit or destroy_bookmarks permissions.

Mitigation: remove edit_bookmarks and destroy_bookmarks from untrusted users, remove private information from bookmark searches.

• Affects Foreman 0.3 and higher
• Fix released in Foreman 1.11.0-RC2 and 1.10.3
• Redmine issue #13828

The popup boxes next to global parameters, smart class parameters and smart variables on the host and host group edit forms can allow stored XSS to be executed in the browser from the parameter description etc.

Mitigation: do not click on the information popup box next to parameters in the host/group forms, and/or remove permission to edit Puppet classes from untrusted users.

• Affects all known Foreman versions
• Fix released in Foreman 1.10.0
• Redmine issue #12611

The search for facts and also hosts by facts is vulnerable to SQL injection by breaking out of quotes in either the fact name or the fact value.

No CVE identifier will be assigned to this vulnerability as it affects only release candidates.

• Affects Foreman 1.10.0-RC1 and higher
• Fix released in Foreman 1.10.0-RC3
• Redmine issue #12458

The parameter management UI has a checkbox to mark values as hidden to mask them from casual viewing. The checkbox that hides/shows the value fails to handle HTML properly and so is vulnerable to an XSS issue where HTML can be stored in a parameter, and executed by another user if they later tick/untick the hide box.

• Affects Foreman 1.7.0 and higher
• Fix released in Foreman 1.10.0-RC1
• Redmine issue #11859

This CVE identifier was assigned before realizing that this was not a bug in Foreman, but a feature of Active Directory. It will remain assigned for future reference only. See the Active Directory password changes section of the manual or Microsoft KB906305 for more details.

When using an Active Directory instance to log into Foreman (via an LDAP authentication source), it is possible to log into Foreman for up to one hour after a password change in AD using the old password.

• Fix to Foreman not required, reconfigure Active Directory
• Redmine issue #11471

Users with view_reports or destroy_reports permissions allows a user to view or delete reports from any host without taking their view_hosts permission into account.

The reports list and other views combine the reports and hosts permissions to only show reports for hosts that a user can view, but the individual report show/delete pages and APIs do not apply the hosts permissions.

Mitigation: remove view_reports and destroy_reports permissions from users until a fix is available, or add a search query to the role filter to restrict it.

• Affects Foreman 1.5.0 and higher
• Fix released in Foreman 1.9.1 and 1.8.4
• Redmine issue #11579

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.

Mitigation: add the following to the Apache HTTP VirtualHost, e.g. in /etc/httpd/conf.d/05-foreman.d/api_request.conf:

RewriteEngine On
RewriteRule ^/api/(.*) https://%{SERVER_NAME}/api/$1 [R,L]

• Affects Foreman 1.1 and higher
• Fix released in Foreman 1.9.0-RC1
• Redmine issue #11119

A user with the edit_users permission (e.g. with the Manager role) is allowed to edit admin users. This allows them to change the password of the admin user's account and gain access to it.

Mitigation: change roles of users with the edit_users permission, remove the Unlimited flag and set a search query of admin = false.

• Affects all known Foreman versions
• Fix released in Foreman 1.9.0-RC1
• Redmine issue #10829

This CVE identifier was assigned before realizing that no released versions of Foreman Discovery were affected. It will remain assigned for future reference only.

The Foreman Discovery plugin auto provisioning rules do not enforce that the rule and the assigned host group are in the same organization and location. This can allow a rule to be configured with mismatched orgs/locations, and for another user who has access to the rule but not the host group, to run it and provision a host into a group in a different org/location to their own.

• Affects no released versions of Foreman Discovery
• Fix released in Foreman Discovery 4.0.0
• Redmine issue #10469

The session cookie created when accessing the Foreman web UI over HTTPS is not set with the 'secure' flag, which may lead to session hijacking.

If a user successfully logs into Foreman, then accesses Foreman over HTTP (which redirects to HTTPS, but with a window of opportunity), the session ID will be sent unencrypted and the session may be hijacked by an attacker.

• Affects all known Foreman versions
• Fix released in Foreman 1.8.1
• Redmine issue #10275

When a non-admin user is associated to organizations or locations, their access is not correctly restricted. API access allows access to resources in any org/location, and UI access when the user is associated to more than one org/location is not restricted.

This allows users to read, edit and perform actions on resources (e.g. hosts) outside of the organizations or locations they have been assigned to.

• Affects Foreman 1.2.0 (TBC) and higher
• Fix released in Foreman 1.8.0-RC3 and 1.7.5
• Redmine issue #9947

When making an SSL connection to an LDAP authentication source in Foreman, the remote server certificate is accepted without any verification against known certificate authorities.

This can allow the LDAP connection between Foreman and the LDAP server to be attacked, and a different LDAP server could be contacted to authenticate users to Foreman.

• Affects Foreman 1.3.0 and higher
• Fix released in Foreman 1.7.4 and 1.8.0-RC2
• Redmine issue #9858

The smart proxy (foreman-proxy) fails to block connections when no client SSL certificate is supplied, instead permitting any request. Typically the smart proxy is configured to receive HTTPS requests with a client SSL certificate that is signed by the same CA (certificate authority) as its own, preventing unauthorized access to manage services such as DHCP, DNS and the Puppet CA.

It is strongly recommended to mitigate the problem by restricting access to the smart proxy. More information on foreman-announce.

Thanks to Michael Moll, Jon McKenzie and Michael Messmore for reporting the issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.6.2 and 1.5.4
• Redmine issue #7822
• Red Hat Bugzilla #1150879

Provisioning templates can store HTML and then evaluate HTML or JS content when using the editor's preview function.

Thanks to Aaron Stone for reporting this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.6.1
• Redmine issue #7483
• Red Hat Bugzilla #1145398

The user logout function could be triggered through cross-site request forgery (e.g. a redirect), causing a user to be logged out and lose their active session.

Thanks to Jan Hutař of Red Hat for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.6.1
• Redmine issue #6999
• Red Hat Bugzilla #1128108

Operating system names and descriptions could store and cause evaluation of HTML in page views, allowing a cross site scripting (XSS) attack against the user.

Thanks to Jan Hutař of Red Hat for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.5.2
• Redmine issue #6580
• Red Hat Bugzilla #1108745

The host YAML page, used to preview the Foreman response for the Puppet ENC, will evaluate HTML stored in any host data such as parameters or comments, allowing a cross site scripting (XSS) attack against the user.

• Affects all known Foreman versions
• Fix released in Foreman 1.4.5 and 1.5.1
• Redmine issue #6149
• Red Hat Bugzilla #1108241

When resources (e.g. a host group) were saved or deleted through the web UI, the name of the resource would be evaluated unsafely inside the notification popup, allowing a cross site scripting (XSS) attack against the user changing the resource.

Thanks to Adam Salah of the Red Hat Satellite 6 QE Team for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.4.5 and 1.5.1
• Redmine issue #5881
• Red Hat Bugzilla #1100313

The Smart Proxy API for downloading boot files from installation media to the TFTP server was vulnerable to remote code execution exploits.

Thanks to Lukas Zapletal of the Red Hat Foreman Team for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.4.5 and 1.5.1
• Redmine issue #6086
• Red Hat Bugzilla #1105369

The search auto-completion was vulnerable to a stored cross site scripting (XSS) attack via completion of (global/host) parameters in search keys.

Thanks to Jan Hutař of Red Hat for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.4.4 and 1.5.0
• Redmine issue #5471
• Red Hat Bugzilla #1094642

Provisioning templates previews ("spoof") are accessible without authentication when used with the hostname parameter.

• Affects Foreman 1.4.0 to 1.4.3 inclusive
• Fix released in Foreman 1.4.4 and 1.5.0
• Redmine issue #5436
• Red Hat Bugzilla #1092354

When Kafo (used in the Foreman installer) runs, a /tmp/default_values.yaml file is written to and created with world readable permissions. This is prone to race-condition attacks and contains default values for all parameters, such as autogenerated passwords.

• Affects all known Kafo versions
• Fix released in Kafo 0.3.17 and 0.5.2 (to Foreman 1.4 and 1.5 repos respectively)
• Redmine issue #4648
• Red Hat Bugzilla #1076335

Upon successful login, a new session ID was not generated for the user, so an attacker who had set the session ID in the request from the user's browser would be able to exploit the escalated session with the user's privileges.

Thanks to Jeremy Choi and Keqin Hong of the Red Hat HSS Pen-Test Team for discovering this issue.

• Affects all known Foreman versions
• Fix released in Foreman 1.4.2
• Redmine issue #4457
• Red Hat Bugzilla #1072151

The 500 error page was vulnerable to stored cross site scripting attacks, where the error message was rendered without HTML encoding. In addition, bookmarks could be saved by any user with HTML in the name which caused an error when rendering the bookmark list, leading to a 500 error and execution of the HTML in the browser.

Thanks to Jeremy Choi and Keqin Hong of the Red Hat HSS Pen-Test Team for discovering this issue.

• Affects Foreman 1.4.0 to 1.4.1 inclusive
• Fix released in Foreman 1.4.2
• Redmine issue #4456
• Red Hat Bugzilla #1071741

Host and host group parameter overrides (lookup_values) allowed SQL injection from the host FQDN or host group label.

• Fix released in Foreman 1.2.3
• Redmine issue #3160
• Red Hat Bugzilla #1013076

The /api/hosts API was found to provide access to all hosts without checking whether the current user has privileges to view a particular host.

Thanks to Daniel Lobato Garcia of CERN IT-PES-PS for discovering this issue.

• Fix released in Foreman 1.2.2
• Redmine issue #2863
• Red Hat Bugzilla #990374

Power and IPMI boot actions converted user input to symbols, which could lead to memory exhaustion.

Thanks to Marek Hulan of the Red Hat Foreman Team for discovering this issue.

• Fix released in Foreman 1.2.2
• Redmine issue #2860
• Red Hat Bugzilla #989755

Bookmarks could be created in Foreman containing data that was later executed arbitrarily when reading the bookmark.

Thanks to Ramon de C Valle of the Red Hat Product Security Team for discovering this issue.

• Fix released in Foreman 1.2.0
• Redmine issue #2631
• Red Hat Bugzilla #968166

Non-admin user with permissions to create or edit other users were able to change the admin flag, or assign roles that they themselves do not have, enabling a privilege escalation.

Thanks to Ramon de C Valle of the Red Hat Product Security Team for discovering this issue.

• Fix released in Foreman 1.2.0
• Redmine issue #2630
• Red Hat Bugzilla #966804

Requests to the smart proxy Puppet run API were not properly escaped when running the Puppet command, leading to possible arbitrary command execution.

• Fix released in Foreman 1.2.0

XMLHttpRequest or AJAX requests to Foreman were not subject to authorization checks, enabling privilege escalation for authenticated users.

• Fix released in Foreman 1.1

The external node classifier (ENC) API in Foreman was accessible to any remote host and the output would contain the hashed root psasword (used for unattended installation). Authentication and authorization features were added to the ENC API to secure this data.

Thanks to Andreas Rogge for discovering this issue.

• Fix released in Foreman 1.1
• Redmine issue #2069

The salt used to hash root passwords (used for unattended installation) was fixed to the string "foreman" instead of being randomized.

• Fix released in Foreman 1.1
• Redmine issue #2069

Fact and report import APIs in Foreman were accessible to any remote host and accepted YAML input, allowing arbitrary objects to be created on the Foreman server via YAML. Authentication and authorization features were added to the import APIs to prevent this.

• Fix released in Foreman 1.1
• Redmine issue #2121

Input to the search mechanism in Foreman was not escaped when constructing queries, enabling SQL injection into the resulting query.

• Fix released in Foreman 1.0.2

The smart proxy daemon ran with a umask of 0, causing files and directories written by it to have world-writable bits set. Files managed by the smart proxy could be modified by local users on the same host.

• Fix released in Foreman 1.1
• Redmine issue #1929

The Foreman project uses multiple GPG keys to sign packages and release artifacts. All stable releases will be signed by one of the keys. Nightly and plugin Debian packages will be signed, while nightly and plugin RPM packages will not (this may change in the future).

Signing for the Debian family of operating systems is via secure apt and more information, including verification steps can be found on the Debian web site. RPMs themselves are signed and can be verified using rpm --checksig PACKAGE. All yum repository configs set up by foreman-release RPMs or the installer will enable GPG checking by default.

Key management is changing at the time of writing to cycle nightly keys every two years, and issue limited duration keys per stable release.

  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/1CC363863DD64AF30638DB79C101586BE0745924.pub">1CC363863DD64AF30638DB79C101586BE0745924</a></td>
    <td>1CC3 6386 3DD6 4AF3 0638  DB79 C101 586B E074 5924</td>
    <td>Foreman Automatic Signing Key (2.3)</td>
    <td style='white-space:nowrap'>2020-11-02</td>
    <td style='white-space:nowrap'>2021-11-02</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/643253F71B82B1BEAF2E1D4FA439BD55AC2AD9F1.pub">643253F71B82B1BEAF2E1D4FA439BD55AC2AD9F1</a></td>
    <td>6432 53F7 1B82 B1BE AF2E  1D4F A439 BD55 AC2A D9F1</td>
    <td>Foreman Automatic Signing Key (2.4)</td>
    <td style='white-space:nowrap'>2021-02-01</td>
    <td style='white-space:nowrap'>2022-02-01</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/7EF7E6EA4022F241BB89A149955C283E7522CC3F.pub">7EF7E6EA4022F241BB89A149955C283E7522CC3F</a></td>
    <td>7EF7 E6EA 4022 F241 BB89  A149 955C 283E 7522 CC3F</td>
    <td>Foreman Automatic Signing Key (2.5)</td>
    <td style='white-space:nowrap'>2021-04-26</td>
    <td style='white-space:nowrap'>2022-04-26</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/C8B9E30B0DBCAB595E98DF5C965467189B776908.pub">C8B9E30B0DBCAB595E98DF5C965467189B776908</a></td>
    <td>C8B9 E30B 0DBC AB59 5E98  DF5C 9654 6718 9B77 6908</td>
    <td>Foreman Automatic Signing Key (3.0)</td>
    <td style='white-space:nowrap'>2021-08-02</td>
    <td style='white-space:nowrap'>2022-08-02</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/5B7C3E5A735BCB4D615829DC0BDDA991FD7AAC8A.pub">5B7C3E5A735BCB4D615829DC0BDDA991FD7AAC8A</a></td>
    <td>5B7C 3E5A 735B CB4D 6158  29DC 0BDD A991 FD7A AC8A</td>
    <td>Foreman Automatic Signing Key (2021)</td>
    <td style='white-space:nowrap'>2021-07-23</td>
    <td style='white-space:nowrap'>2023-07-23</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/1CD4BC6A65EB598E53C66E176A3BF4ED1434F5D3.pub">1CD4BC6A65EB598E53C66E176A3BF4ED1434F5D3</a></td>
    <td>1CD4 BC6A 65EB 598E 53C6  6E17 6A3B F4ED 1434 F5D3</td>
    <td>Foreman Automatic Signing Key (3.1)</td>
    <td style='white-space:nowrap'>2021-11-09</td>
    <td style='white-space:nowrap'>2022-11-09</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/77F7076DFD4F373EF0F0E9AC8D746ED06DA7EB32.pub">77F7076DFD4F373EF0F0E9AC8D746ED06DA7EB32</a></td>
    <td>77F7 076D FD4F 373E F0F0  E9AC 8D74 6ED0 6DA7 EB32</td>
    <td>Foreman Automatic Signing Key (3.2)</td>
    <td style='white-space:nowrap'>2022-02-07</td>
    <td style='white-space:nowrap'>2023-02-07</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
   <tr>
    <td><a href="{{ site.baseurl }}/static/keys/5E77807805888E7F2F31A50E8321CBCA2A6A4BAA.pub">5E77807805888E7F2F31A50E8321CBCA2A6A4BAA</a></td>
    <td>5E77 8078 0588 8E7F 2F31  A50E 8321 CBCA 2A6A 4BAA</td>
    <td>Foreman Automatic Signing Key (3.3)</td>
    <td style='white-space:nowrap'>2022-05-03</td>
    <td style='white-space:nowrap'>2023-05-03</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/2A6F745AA62DE481567D3AF639D12077F120E13E.pub">2A6F745AA62DE481567D3AF639D12077F120E13E</a></td>
    <td>2A6F 745A A62D E481 567D 3AF6 39D1 2077 F120 E13E</td>
    <td>Foreman Automatic Signing Key (3.4)</td>
    <td style='white-space:nowrap'>2022-08-05</td>
    <td style='white-space:nowrap'>2023-08-05</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/51B9D1D1BADA3F001C8774046F7F9C618F5CA95B.pub">51B9D1D1BADA3F001C8774046F7F9C618F5CA95B</a></td>
    <td>51B9 D1D1 BADA 3F00 1C87  7404 6F7F 9C61 8F5C A95B</td>
    <td>Foreman Automatic Signing Key (3.5)</td>
    <td style='white-space:nowrap'>2022-11-07</td>
    <td style='white-space:nowrap'>2023-11-07</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/A21D56E01064415EDC8FC7597803ABC5FED77E93.pub">A21D56E01064415EDC8FC7597803ABC5FED77E93</a></td>
    <td>A21D 56E0 1064 415E DC8F  C759 7803 ABC5 FED7 7E93</td>
    <td>Foreman Automatic Signing Key (3.6)</td>
    <td style='white-space:nowrap'>2023-02-21</td>
    <td style='white-space:nowrap'>2024-02-21</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/DC71C75A8B5438E972C645078FCB3EC0BDCC85AE.pub">DC71C75A8B5438E972C645078FCB3EC0BDCC85AE</a></td>
    <td>DC71 C75A 8B54 38E9 72C6  4507 8FCB 3EC0 BDCC 85AE</td>
    <td>Foreman Automatic Signing Key (3.7)</td>
    <td style='white-space:nowrap'>2023-05-16</td>
    <td style='white-space:nowrap'>2024-05-15</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/79AAD6C6E922580DBC7BF46A0959620CCBE50FBE.pub">79AAD6C6E922580DBC7BF46A0959620CCBE50FBE</a></td>
    <td>79AA D6C6 E922 580D BC7B  F46A 0959 620C CBE5 0FBE</td>
    <td>Foreman Automatic Signing Key (3.8)</td>
    <td style='white-space:nowrap'>2023-08-22</td>
    <td style='white-space:nowrap'>2023-08-21</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/7EC13BEC88DA66692700BB9ACD9851C256641D7B.pub">7EC13BEC88DA66692700BB9ACD9851C256641D7B</a></td>
    <td>7EC1 3BEC 88DA 6669 2700  BB9A CD98 51C2 5664 1D7B</td>
    <td>Foreman Automatic Signing Key (3.9)</td>
    <td style='white-space:nowrap'>2023-11-14</td>
    <td style='white-space:nowrap'>2024-11-13</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/63B38BE51B2DDDAFF7EF7EC90A8F8D4093DD1D0C.pub">63B38BE51B2DDDAFF7EF7EC90A8F8D4093DD1D0C</a></td>
    <td>63B3 8BE5 1B2D DDAF F7EF  7EC9 0A8F 8D40 93DD 1D0C</td>
    <td>Foreman Automatic Signing Key (3.10)</td>
    <td style='white-space:nowrap'>2024-02-20</td>
    <td style='white-space:nowrap'>2025-02-19</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
  <tr>
    <td><a href="{{ site.baseurl }}/static/keys/CD41E7A87E353C3A26F891D24E7082461790A6E6.pub">CD41E7A87E353C3A26F891D24E7082461790A6E6</a></td>
    <td>CD41 E7A8 7E35 3C3A 26F8  91D2 4E70 8246 1790 A6E6</td>
    <td>Foreman Automatic Signing Key (3.11)</td>
    <td style='white-space:nowrap'>2024-05-20</td>
    <td style='white-space:nowrap'>2024-05-19</td>
    <td style='white-space:nowrap'></td>
    <td></td>
  </tr>
</tbody>

In July 2014 after a server was compromised, the existing GPG key (0xE775FF07) was revoked and replaced with a new key (0x1AA043B8) as a precaution. All existing packages were re-signed with the new key and thereafter, new major releases are signed with new per-release keys.

All users with the old key trusted are urged to immediately disable this as follows:

• Debian users must run sudo apt-key del E775FF07
• RPM users must run sudo rpm -e gpg-pubkey-e775ff07-4cda3cf9

More information is available in the announcement.