CVE-2024-53349
First published: Fri Mar 21 2025(Updated: )
Insecure permissions in kuadrant v0.11.3 allow attackers to gain access to the service account's token, leading to escalation of privileges via the secretes component in the k8s cluster
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Kuadrant | ||
| Kuadrant | <=0.11.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-53349?
The severity of CVE-2024-53349 is considered high due to the potential for privilege escalation.
How do I fix CVE-2024-53349?
To fix CVE-2024-53349, ensure proper permissions are set on service accounts to prevent unauthorized access.
What does CVE-2024-53349 allow an attacker to do?
CVE-2024-53349 allows attackers to access the service account's token, leading to potential privilege escalation in the Kubernetes cluster.
Which versions of Kuadrant are affected by CVE-2024-53349?
CVE-2024-53349 affects Kuadrant version 0.11.3.
What component in Kubernetes is exploited in CVE-2024-53349?
The secrets component in the Kubernetes cluster is exploited in CVE-2024-53349.
- agent/references
- agent/first-publish-date
- agent/description
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/source
- agent/author
- agent/severity
- agent/weakness
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/kuadrant
- canonical/kuadrant
- vendor/linuxfoundation
- version/kuadrant/0.11.3