Member-to-root escalation via unchecked user role assignment
Published Feb 8, 2024 · Updated Aug 27, 2025
Improper authorization in OpenObserve before 0.8.0 allows remote authenticated users to create organization users with root privileges. The POST /api/{org_id}/users handler accepts the caller-supplied role in the user-creation payload without validating that a member may assign it. A regular organization member can therefore create a new root account and obtain unauthorized control of application resources and data.
Summary
What happened
Improper authorization in OpenObserve before 0.8.0 allows remote authenticated users to create organization users with root privileges. The POST /api/{org_id}/users handler accepts the caller-supplied role in the user-creation payload without validating that a member may assign it. A regular organization member can therefore create a new root account and obtain unauthorized control of application resources and data.
The record
- CVE
- CVE-2024-24830
- Published
- Feb 8, 2024
- Updated
- Aug 27, 2025
- Vendor
- OpenObserve
- Product
- OpenObserve
- Classifications
- CWE-285, CWE-284, CWE-272, CWE-269, CWE-287, T1136
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.0
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
- Vendor-published users API proof of conceptproof of concept · demonstrated
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