OneUptime: Untrusted Code Execution in Synthetic Monitors

Summary

A software update is available to fix a security risk in OneUptime's Synthetic Monitors. In older versions, an attacker could run malicious code on OneUptime servers, potentially accessing sensitive database credentials and taking control of the system. Update to version 10.0.18 or later to resolve this issue.

What to do

Update oneuptime common to version 10.0.18.

Affected software

Vendor	Product	Affected versions	Fix available
oneuptime	common	<= 10.0.18	10.0.18
hackerbay	oneuptime	<= 10.0.18	–

Original title

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websi...

Original description

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js vm module. By leveraging a standard prototype-chain escape (this.constructor.constructor), an attacker can bypass the sandbox, gain access to the underlying Node.js process object, and execute arbitrary system commands (RCE) on the oneuptime-probe container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise. This vulnerability is fixed in 10.0.18.

ghsa CVSS3.1 10.0

Vulnerability type

CWE-94 Code Injection