# CVE-2023-49805: Uptime Kuma Missing Origin Validation in WebSockets > Attackers can bypass firewall protections and access the application via cross-origin WebSocket connections, especially in no-auth mode. - **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 11 Dec 2023 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-mj22-23ff-2hrr ## What is CVE-2023-49805? CVE-2023-49805 is a medium-severity vulnerability in louislam uptime-kuma, published on 11 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description 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`. Weakness: CWE-346 (Origin Validation Error), CWE-1385 (Missing Origin Validation in WebSockets) ## Which versions are affected by CVE-2023-49805? It affects 2 products. Products: Dockge.kuma Dockge, Uptime.kuma Uptime Kuma. ## How do I fix CVE-2023-49805? No fix has been published for CVE-2023-49805 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-49805 being exploited? There is no known exploitation of CVE-2023-49805 in the wild and no public exploit code. ## Other vulnerabilities in louislam uptime-kuma - [CVE-2023-49804](https://insights.sbomify.com/CVE-2023-49804/): Uptime Kuma Password Change Vulnerability (medium 6.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-49805 and fix it if it is affected. What it is: CVE-2023-49805 is a medium-severity vulnerability in louislam uptime-kuma, published on 11 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-49805 in the wild and no public exploit code. Affected product: louislam uptime-kuma. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-49805/ (Markdown: https://insights.sbomify.com/CVE-2023-49805/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49805 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49805 - OSV: https://osv.dev/vulnerability/CVE-2023-49805 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-49805/ Summaries are generated and may contain mistakes; the official description above is the record.