Cluster-admin escalation via fence-agent path injection
Published Aug 12, 2024 · Updated Feb 25, 2026
Code injection in Fence Agents Remediation Operator 0.4.0 before 0.4.1-22 allows remote authenticated users to execute commands in its pod. The operator passes attacker-controlled --ssh-path or --telnet-path values from a crafted FenceAgentsRemediation resource to an SSH/Telnet fence agent as executable commands. Developer-level permission to create that resource is sufficient to gain the operator service account and then a cluster-admin service account.
Summary
What happened
Code injection in Fence Agents Remediation Operator 0.4.0 before 0.4.1-22 allows remote authenticated users to execute commands in its pod. The operator passes attacker-controlled --ssh-path or --telnet-path values from a crafted FenceAgentsRemediation resource to an SSH/Telnet fence agent as executable commands. Developer-level permission to create that resource is sufficient to gain the operator service account and then a cluster-admin service account.
The record
- CVE
- CVE-2024-5651
- Published
- Aug 12, 2024
- Updated
- Feb 25, 2026
- Vendor
- 389 Directory Server
- Product
- Fence Agents Remediation Operator
- Classifications
- CWE-94, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2024CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record 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=0.4.0 <0.4.1-22
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