References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Known Affected Software Configurations Switch to CPE 2.2

Change History

OR
          *cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:* versions up to (excluding) 10.0.21

GitHub, Inc.: https://github.com/OneUptime/oneuptime/releases/tag/10.0.21 Types: Product, Release Notes

GitHub, Inc.: https://github.com/OneUptime/oneuptime/security/advisories/GHSA-jw8q-gjvg-8w4q Types: Exploit, Vendor Advisory

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the oneuptime-probe server/container. The root cause is that untrusted Synthetic Monitor code is executed inside Node's vm while live host-realm Playwright browser and page objects are exposed to it. A malicious user can call Playwright APIs on the injected browser object and cause the probe to spawn an attacker-controlled executable. This is a server-side remote code execution issue. It does not require a separate vm sandbox escape. This vulnerability is fixed in 10.0.21.

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CWE-749

https://github.com/OneUptime/oneuptime/releases/tag/10.0.21

https://github.com/OneUptime/oneuptime/security/advisories/GHSA-jw8q-gjvg-8w4q