Is CVE-2024-29194 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-29194 being exploited in the wild.

How severe is CVE-2024-29194?

Low severity, with a CVSS score of 3.1, published 25 March 2024.

Which products and versions are affected?

@oneuptime/common-server (npm) SEMVER:introduced=0,fixed=7.0.1815; @oneuptime/model (npm) SEMVER:introduced=0,fixed=7.0.1815; OneUptime >= 7.0.1803, < 7.0.1815.

Is there a fix for CVE-2024-29194?

Yes. @oneuptime/common-server (npm): upgrade to 7.0.1815 or later; @oneuptime/model (npm): upgrade to 7.0.1815 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-29194 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2024-29194?

Check whether you run @oneuptime/common-server (npm), @oneuptime/model (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-29194: OneUptime privilege escalation via local storage manipulation

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

Yes. @oneuptime/common-server (npm): upgrade to 7.0.1815 or later; @oneuptime/model (npm): upgrade to 7.0.1815 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2024-29194 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2024-29194?

Check whether you run @oneuptime/common-server (npm), @oneuptime/model (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-29194 · Severity: low · CVSS 3.1 · Published 2024-03-25

OneUptime, an open-source monitoring and observability platform, is vulnerable to a flaw that allows standard users to gain administrative access. By simply modifying a value in their browser's local storage, an authenticated user can trick the system into granting them elevated permissions. This could allow unauthorized individuals to view sensitive information, such as the full list of registered users on the platform.

Technologies: OneUptime. Vendors: npm, OneUptime.

Quick answers

Is CVE-2024-29194 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-29194 being exploited in the wild.
How severe is CVE-2024-29194?: Low severity, with a CVSS score of 3.1, published 25 March 2024.
Which products and versions are affected?: @oneuptime/common-server (npm) SEMVER:introduced=0,fixed=7.0.1815; @oneuptime/model (npm) SEMVER:introduced=0,fixed=7.0.1815; OneUptime >= 7.0.1803, < 7.0.1815.
Is there a fix for CVE-2024-29194?: Yes. @oneuptime/common-server (npm): upgrade to 7.0.1815 or later; @oneuptime/model (npm): upgrade to 7.0.1815 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-29194 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2024-29194?: Check whether you run @oneuptime/common-server (npm), @oneuptime/model (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@oneuptime/common-server (npm): upgrade to 7.0.1815 or later
```
npm install @oneuptime/common-server@7.0.1815
```
@oneuptime/model (npm): upgrade to 7.0.1815 or later
```
npm install @oneuptime/model@7.0.1815
```

Technical details

A privilege escalation vulnerability exists in OneUptime due to improper server-side validation of authorization flags stored in the browser's local storage. Specifically, the application relies on the 'is_master_admin' key within local storage to determine administrative status. An authenticated attacker can use browser developer tools to manually change this key from 'false' to 'true'. Because the backend fails to verify this status against its own records, the attacker gains access to administrative functionalities, including the ability to view the complete list of registered users. The issue is addressed in version 7.0.1815 by implementing proper server-side checks.

Affected products

OneUptime OneUptime >= 7.0.1803, < 7.0.1815

Identifiers

CVE-2024-29194
GHSA-246p-xmg8-wmcq

Timeline

2024-03-22: patched: Fix committed to repository
2024-03-24: disclosed: NVD and GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.