Credential disclosure via Proxmox API
Published Jun 7, 2021 · Updated Aug 3, 2024
Information disclosure in Foreman Fog Proxmox before 0.13.1 allows local users to read Proxmox credentials through the API. The Proxmox compute-resource API includes the resource password in responses under /api/compute_resources/ and /api/compute_resources/:id/ instead of filtering it. An authenticated user with view_compute_resource permission can retrieve the secret, exposing connected Proxmox resources to confidentiality, integrity, and availability compromise.
Summary
What happened
Information disclosure in Foreman Fog Proxmox before 0.13.1 allows local users to read Proxmox credentials through the API. The Proxmox compute-resource API includes the resource password in responses under /api/compute_resources/ and /api/compute_resources/:id/ instead of filtering it. An authenticated user with view_compute_resource permission can retrieve the secret, exposing connected Proxmox resources to confidentiality, integrity, and availability compromise.
The record
- CVE
- CVE-2021-20259
- Published
- Jun 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Foreman Project
- Product
- Foreman Fog Proxmox
- Classifications
- CWE-200, T1213
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 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=before foreman_fog_proxmox 0.13.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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