OneUptime Vulnerable to a Privilege Escalation via Local Storage Key Manipulation

published 2024-03-24 2 y ago modified 2026-09-10 1 mo ago also GHSA-246p-xmg8-wmcq , EUVD-2024-0783

cvss: 8.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

OneUptime is a solution for monitoring and managing online services. The vulnerability lies in the improper validation of client-side stored data within the web application. Specifically, the is_master_admin key, stored in the local storage of the browser, can be manipulated by an attacker. By changing this key from false to true, the application grants administrative privileges to the user, without proper server-side validation. This has been patched in 7.0.1815.

Patch / fix

fixed in 3 links 1

npm @oneuptime/model 7.0.1815
npm @oneuptime/common-server 7.0.1815
OneUptime oneuptime 7.0.1815

github.com/OneUptime/oneuptime@14016d2 commit

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-03-25)

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/OneUptime/oneuptime/security/advisories/GHSA-246p-xmg8-wmcq referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
GitHub	3.1	8.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	@oneuptime/model	<7.0.1815	7.0.1815
npm	@oneuptime/common-server	<7.0.1815	7.0.1815

Affected products

OneUptime oneuptime

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

github.com /OneUptime/oneuptime/commit/14016d23d834038dd65d3a96cf71af04b556a32c
web, patch
github.com /OneUptime/oneuptime/security/advisories/GHSA-246p-xmg8-wmcq
web, exploit, release-notes
nvd.nist.gov /vuln/detail/CVE-2024-29194
advisory
github.com /OneUptime/oneuptime
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary