OneUptime Synthetic Monitors allow malicious code execution on probes

Summary

A security issue in OneUptime Synthetic Monitors before version 10.0.20 allows unauthorized users to run malicious code on monitoring probes. This could lead to unauthorized access to sensitive information or disruption of monitoring services. OneUptime has released a fix in version 10.0.20 to address this issue.

What to do

Update oneuptime common to version 10.0.20.

Affected software

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

Original title

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.20, OneUptime Synthetic Monitors allow low-privileged project users to submit custom Playwright code that is execu...

Original description

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.20, OneUptime Synthetic Monitors allow low-privileged project users to submit custom Playwright code that is executed on the oneuptime-probe service. In the current implementation, this untrusted code is run inside Node's vm and is given live host Playwright objects such as browser and page. This creates a distinct server-side RCE primitive: the attacker does not need the classic this.constructor.constructor(...) sandbox escape. Instead, the attacker can directly use the injected Playwright browser object to reach browser.browserType().launch(...) and spawn an arbitrary executable on the probe host/container. This vulnerability is fixed in 10.0.20.

ghsa CVSS3.1 10.0

Vulnerability type

CWE-749