Quick answers
- Is CVE-2023-36822 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-36822 being exploited in the wild.
- How severe is CVE-2023-36822?
- Low severity, with a CVSS score of 3.1, published 1 May 2024.
- Which products and versions are affected?
- uptime-kuma (npm) SEMVER:introduced=0,fixed=1.22.1.
- Is there a fix for CVE-2023-36822?
- Yes. uptime-kuma (npm): upgrade to 1.22.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2023-36822 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2023-36822?
- Check whether you run uptime-kuma (npm) 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
- uptime-kuma (npm): upgrade to 1.22.1 or later
npm install uptime-kuma@1.22.1
Technical details
The vulnerability is a path traversal flaw (CWE-22) in the plugin installation mechanism. When installing a plugin, the application constructs a file path using a user-supplied plugin name without proper validation or sanitization. Before downloading a plugin, the code checks if the installation directory exists and removes it recursively using fs.rmSync(). An attacker can bypass directory restrictions by using path traversal sequences (e.g., "../../../") in the plugin name parameter to reference and delete files outside the intended plugins directory. Exploitation requires authentication (low privilege) and network access to the WebSocket API endpoint. A successful attack can delete critical system files, causing service disruption and data loss. The vulnerability was fixed in version 1.22.1.
Affected products
- Louis Lam Uptime Kuma <= 1.22.0
Identifiers
- CVE-2023-36822
- GHSA-vr8x-74pm-6vj7
Timeline
- 2023-07-04: disclosed
- 2024-05-01: advisory
- 2023: patched: Fixed in version 1.22.1