What is CVE-2024-29194?

CVE-2024-29194 is a high-severity security vulnerability in @oneuptime/model (npm), affecting versions < 7.0.1815. It is fixed in 7.0.1815.

How severe is CVE-2024-29194?

CVE-2024-29194 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2024-29194?

@oneuptime/model (npm) versions < 7.0.1815; @oneuptime/common-server (npm) versions < 7.0.1815.

Is there a fix for CVE-2024-29194?

Yes. CVE-2024-29194 is fixed in 7.0.1815. Upgrade to this version or later.

Is CVE-2024-29194 exploitable, and should I be worried?

Whether CVE-2024-29194 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-29194 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-29194?

Upgrade: @oneuptime/model to 7.0.1815 or later, @oneuptime/common-server to 7.0.1815 or later.

CVE-2024-29194 in @oneuptime/model

Q: How severe is CVE-2024-29194?

CVE-2024-29194 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2024-29194?

@oneuptime/model (npm) versions < 7.0.1815; @oneuptime/common-server (npm) versions < 7.0.1815.

Q: Is there a fix for CVE-2024-29194?

Yes. CVE-2024-29194 is fixed in 7.0.1815. Upgrade to this version or later.

Q: Is CVE-2024-29194 exploitable, and should I be worried?

Whether CVE-2024-29194 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-29194 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-29194?

Upgrade: @oneuptime/model to 7.0.1815 or later, @oneuptime/common-server to 7.0.1815 or later.

Summary

OneUptime Vulnerable to a Privilege Escalation via Local Storage Key Manipulation

A security vulnerability exists in oneuptime's local storage handling, where a regular user can escalate privileges by modifying the is_master_admin key to true. This allows unauthorized access to administrative functionalities.

Details

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.

POC

(I am using Firefox Developer to demonstrate this vulnerability)
Log in as a normal user. Open developer tools (hit F12), click Storage, then Local Storage. Modify the is_master_admin key from false to true.

Impact

This vulnerability represents a high security risk as it allows any authenticated user to gain administrative privileges through client-side manipulation. Most of the admin previlages were disabled except the user list. Where an attacker could see all the list of users who signed up to OneUptome.

CVE-2024-29194 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.1815); upgrading removes the vulnerable code path.

Affected versions

@oneuptime/model (< 7.0.1815) @oneuptime/common-server (< 7.0.1815)

Security releases

@oneuptime/model → 7.0.1815 (npm) @oneuptime/common-server → 7.0.1815 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This has been patched in 7.0.1815

Frequently Asked Questions

What is CVE-2024-29194? CVE-2024-29194 is a high-severity security vulnerability in @oneuptime/model (npm), affecting versions < 7.0.1815. It is fixed in 7.0.1815.
How severe is CVE-2024-29194? CVE-2024-29194 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2024-29194?
- @oneuptime/model (npm) (versions < 7.0.1815)
- @oneuptime/common-server (npm) (versions < 7.0.1815)
Is there a fix for CVE-2024-29194? Yes. CVE-2024-29194 is fixed in 7.0.1815. Upgrade to this version or later.
Is CVE-2024-29194 exploitable, and should I be worried? Whether CVE-2024-29194 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-29194 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-29194?
- Upgrade @oneuptime/model to 7.0.1815 or later
- Upgrade @oneuptime/common-server to 7.0.1815 or later