CVE-2023-49805: Uptime Kuma Missing Origin Validation in WebSockets
First published: Mon Dec 11 2023(Updated: )
Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, the application uses WebSocket (with Socket.io), but it does not verify that the source of communication is valid. This allows third-party website to access the application on behalf of their client. When connecting to the server using Socket.IO, the server does not validate the `Origin` header leading to other site being able to open connections to the server and communicate with it. Other websites still need to authenticate to access most features, however this can be used to circumvent firewall protections made in place by people deploying the application. Without origin validation, Javascript executed from another origin would be allowed to connect to the application without any user interaction. Without login credentials, such a connection is unable to access protected endpoints containing sensitive data of the application. However, such a connection may allow attacker to further exploit unseen vulnerabilities of the application. Users with "No-auth" mode configured who are relying on a reverse proxy or firewall to provide protection to the application would be especially vulnerable as it would grant the attacker full access to the application. In version 1.23.9, additional verification of the HTTP Origin header has been added to the socket.io connection handler. By default, if the `Origin` header is present, it would be checked against the Host header. Connection would be denied if the hostnames do not match, which would indicate that the request is cross-origin. Connection would be allowed if the `Origin` header is not present. Users can override this behavior by setting environment variable `UPTIME_KUMA_WS_ORIGIN_CHECK=bypass`.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Docke.kuma | <1.3.3 | |
| Uptime Kuma | <1.23.9 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-49805?
CVE-2023-49805 is considered a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2023-49805?
To fix CVE-2023-49805, update Uptime Kuma to version 1.23.10 or later, which addresses the WebSocket validation issue.
What are the implications of CVE-2023-49805?
CVE-2023-49805 allows third-party websites to access the application, potentially leading to data leaks or unauthorized control.
What versions are affected by CVE-2023-49805?
CVE-2023-49805 affects Uptime Kuma versions prior to 1.23.9.
How can I check if my Uptime Kuma instance is vulnerable to CVE-2023-49805?
Check your Uptime Kuma version against the affected versions to see if you need to update to mitigate CVE-2023-49805.
- agent/weakness
- agent/references
- agent/type
- agent/event
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/remedy
- agent/severity
- agent/title
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-api
- agent/software-canonical-lookup-request
- vendor/dockge.kuma
- canonical/docke.kuma
- vendor/uptime.kuma
- canonical/uptime kuma