Privilege escalation via exposed service-account token
Published Mar 21, 2025 · Updated Mar 24, 2025
Improper privilege management in Kuadrant 0.11.3 allows remote attackers to obtain a service-account token and escalate privileges. The published record identifies insecure permissions in the Kubernetes Secrets component but does not disclose the exact RBAC rule or operation that exposes the token. Exploitation requires network reachability and a high-complexity path, and the stolen token grants the service account's existing cluster permissions without reported availability impact.
Summary
What happened
Improper privilege management in Kuadrant 0.11.3 allows remote attackers to obtain a service-account token and escalate privileges. The published record identifies insecure permissions in the Kubernetes Secrets component but does not disclose the exact RBAC rule or operation that exposes the token. Exploitation requires network reachability and a high-complexity path, and the stolen token grants the service account's existing cluster permissions without reported availability impact.
The record
- CVE
- CVE-2024-53349
- Published
- Mar 21, 2025
- Updated
- Mar 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1552.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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