Authenticated proxy impersonation via unchecked SAN signing
Published Jun 3, 2021 · Updated Aug 3, 2024
Incorrect authorization in Foreman before 2.3.4 and before 2.4.0 allows remote authenticated users to impersonate its Smart Proxy. When SAN authorization extensions are enabled, the Puppet CA signs authenticated requests containing attacker-chosen SANs without verifying that those names belong to the requester. The path requires Puppet CA integration and the non-default allow-authorization-extensions setting, after which the issued certificate is trusted as the proxy.
Summary
What happened
Incorrect authorization in Foreman before 2.3.4 and before 2.4.0 allows remote authenticated users to impersonate its Smart Proxy. When SAN authorization extensions are enabled, the Puppet CA signs authenticated requests containing attacker-chosen SANs without verifying that those names belong to the requester. The path requires Puppet CA integration and the non-default allow-authorization-extensions setting, after which the issued certificate is trusted as the proxy.
The record
- CVE
- CVE-2021-3469
- Published
- Jun 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Foreman Project
- Product
- Foreman
- Classifications
- CWE-863, T1649
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=foreman 2.3.4, foreman 2.4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo