CVE-2024-36542
First published: Thu Jul 25 2024(Updated: )
Insecure permissions in kuma v2.7.0 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Uptime Kuma |
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.
Frequently Asked Questions
What is the severity of CVE-2024-36542?
CVE-2024-36542 is considered a high-severity vulnerability due to the potential for data exposure and privilege escalation.
How do I fix CVE-2024-36542?
To fix CVE-2024-36542, ensure proper permission settings are applied to sensitive resources and review service account access controls.
What kind of data is vulnerable in CVE-2024-36542?
CVE-2024-36542 potentially exposes sensitive data that can be accessed by unauthorized attackers due to insecure permissions.
Who is affected by CVE-2024-36542?
CVE-2024-36542 affects users of Kuma version 2.7.0, specifically those utilizing service accounts with insecure permissions.
Can CVE-2024-36542 lead to privilege escalation?
Yes, CVE-2024-36542 allows attackers to escalate privileges by obtaining the service account's token due to improper permission settings.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/severity
- agent/weakness
- collector/nvd-api
- source/NVD
- agent/event
- agent/source
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/kuma
- canonical/uptime kuma