LiveActive security incident?Get immediate response
CVE Record

CVE-2021-3469: Foreman versions before 2.3.4 and before 2.4.0 is affected by an improper authorization handling flaw.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is an authorization flaw in Foreman. An authenticated attacker may be able to impersonate foreman-proxy, but only where Puppet CA SAN signing has been enabled through non-default configuration. The public bundle does not provide CVSS, confirmed exploitation, or detailed remediation beyond affected version boundaries.

Executive priority

Treat this as a configuration-dependent exposure check rather than a broad emergency. Prioritize environments where Foreman manages sensitive infrastructure and Puppet CA SAN signing was enabled.

Technical view

CVE-2021-3469 is CWE-863 improper authorization in Foreman versions before 2.3.4 and before 2.4.0. If Puppet Certificate Authority signing for subject alternative names is enabled, an authenticated attacker can impersonate foreman-proxy. Sources state SANs are not enabled by default and allow-authorization-extensions is false unless explicitly changed.

Likely exposure

Exposure is most likely in Foreman deployments using Puppet CA where administrators explicitly enabled SAN authorization extensions. Default configurations described in the source bundle appear less exposed.

Exploitation context

The source bundle does not cite active exploitation, and CISA KEV status is false. Exploitation requires authentication plus a non-default Puppet CA configuration allowing SAN-related authorization extensions.

Researcher notes

Evidence is limited to the CVE description and Red Hat Bugzilla reference. No CVSS vector, proof of exploitation, or detailed patch notes are included in the supplied bundle. Avoid assuming broader Puppet or Foreman components are affected beyond the stated conditions.

Mitigation direction

  • Identify Foreman deployments older than 2.3.4 or 2.4.0.
  • Check vendor guidance and move affected Foreman instances to a non-affected release.
  • Review Puppet CA configuration for SAN authorization extensions.
  • Disable SAN signing behavior unless explicitly required and approved.
  • Restrict authenticated access to Foreman administrative functions.

Validation and detection

  • Inventory Foreman versions across production and management networks.
  • Review /etc/puppetlabs/puppetserver/conf.d/ca.conf for allow-authorization-extensions changes.
  • Confirm whether Puppet CA SAN signing is enabled.
  • Check access logs for unusual authenticated certificate request activity.
  • Verify Foreman upgrade status against vendor advisory boundaries.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-3469 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aForemanforeman 2.3.4, foreman 2.4.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.