CVE-2021-3469: Medium severity theforeman foreman vulnerability

Published Mar 26, 2021
·
Updated

Foreman versions before 2.3.4 and before 2.4.0 is affected by an improper authorization handling flaw. An authenticated attacker can impersonate the foreman-proxy if product enable the Puppet Certificate authority (CA) to sign certificate requests that have subject alternative names (SANs). Foreman do not enable SANs by default and allow-authorization-extensions is set to false unless user change /etc/puppetlabs/puppetserver/conf.d/ca.conf configuration explicitly.

Other sources

The SmartProxyAuth of the Foreman allows controllers to authenticate certain requests based on the client certificate. As Puppet CA will consider subject alternative names (SANs) from a certificate along with Common name (CN); Puppet CA will sign the certificate with SANs pointing at DNS names of the already existing certificate. An attacker can obtain a new certificate by crafting Certificate Signing Request (CSR) made up with CN & SSNs and can able to impersonation foreman-proxy to accept the request.

Red Hat

Affected Software

3 affected componentsFixes available
redhat/foreman<2.3.4
2.3.4
redhat/foreman<2.4.0
2.4.0
theforeman foreman<2.3.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/foreman to a version that resolves this vulnerability.

    Fixed in 2.3.4
  2. Upgrade

    Upgrade redhat/foreman to a version that resolves this vulnerability.

    Fixed in 2.4.0
  3. Upgrade

    Upgrade Foreman to a version that resolves this vulnerability.

    Fixed in 2.3.4
  4. Upgrade

    Upgrade Foreman to a version that resolves this vulnerability.

    Fixed in 2.4.0
  5. Configuration

    Ensure allow-authorization-extensions is set to false in /etc/puppetlabs/puppetserver/conf.d/ca.conf to prevent Puppet CA from authorizing/signing certificate requests with SANs in a way that enables impersonation of foreman-proxy.

    Puppet Server CA (/etc/puppetlabs/puppetserver/conf.d/ca.conf) allow-authorization-extensions = false
  6. Compensating control

    Use the SmartProxyAuth behavior of Foreman (client certificate-based authentication) to ensure only controllers are allowed to authenticate requests based on the client certificate.

Event History

Jun 3, 2021
CVE Published
via MITRE·07:43 PM
Data Sourced
via MITRE·07:43 PM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2021-3469?

CVE-2021-3469 is a vulnerability in Foreman versions before 2.3.4 and before 2.4.0 that allows an authenticated attacker to impersonate the foreman-proxy if the product enables the Puppet Certificate authority (CA) to sign certificate requests with subject alternative names (SANs).

2

How does CVE-2021-3469 impact Foreman?

CVE-2021-3469 can be exploited by an authenticated attacker to impersonate the foreman-proxy and perform unauthorized actions.

3

What is the severity of CVE-2021-3469?

CVE-2021-3469 has a severity rating of medium (5.4) based on the Common Vulnerability Scoring System (CVSS) v3.0.

4

Which versions of Foreman are affected by CVE-2021-3469?

Foreman versions before 2.3.4 and before 2.4.0 are affected by CVE-2021-3469.

5

How can the CVE-2021-3469 vulnerability be mitigated?

To mitigate CVE-2021-3469, users are advised to upgrade their Foreman software to version 2.3.4 or higher.

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