API token exposure via undisclosed permission flaw
Published Nov 18, 2021 · Updated Aug 3, 2024
Information disclosure in Puppet Continuous Delivery before 4.10.0 allows remote authenticated users to access a Puppet Enterprise API token. Puppet has not published the affected endpoint, function, or permission-check failure that exposes the token to a lower-privileged account. A valid lower-privileged CD4PE account is required; the disclosed consequence is unauthorized possession of a Puppet Enterprise API token.
Summary
What happened
Information disclosure in Puppet Continuous Delivery before 4.10.0 allows remote authenticated users to access a Puppet Enterprise API token. Puppet has not published the affected endpoint, function, or permission-check failure that exposes the token to a lower-privileged account. A valid lower-privileged CD4PE account is required; the disclosed consequence is unauthorized possession of a Puppet Enterprise API token.
The record
- CVE
- CVE-2021-27024
- Published
- Nov 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Puppet
- Product
- Continuous Delivery
- Classifications
- T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 18, 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=CD4PE prior to 4.10.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