CVE-2024-42467: CometVisu Backend for openHAB affected by SSRF/XSS
openHAB, a provider of open-source home automation software, has add-ons including the visualization add-on CometVisu. In versions 3.4.0.M4 through 4.2.0,, the proxy endpoint of openHAB's CometVisu add-on can be accessed without authentication. This proxy-feature can be exploited as Server-Side Request Forgery (SSRF) to induce GET HTTP requests to internal-only servers, in case openHAB is exposed in a non-private network. Furthermore, this proxy-feature can also be exploited as a Cross-Site Scripting (XSS) vulnerability, as an attacker is able to re-route a request to their server and return a page with malicious JavaScript code. Since the browser receives this data directly from the openHAB CometVisu UI, this JavaScript code will be executed with the origin of the CometVisu UI. This allows an attacker to exploit call endpoints on an openHAB server even if the openHAB server is located in a private network. (e.g. by sending an openHAB admin a link that proxies malicious JavaScript.) This issue may lead up to Remote Code Execution (RCE) when chained with other vulnerabilities. Users should upgrade to version 4.2.1 of the CometVisu add-on of openHAB to receive a patch.
Security readout for executives and security teams
Plain-English summary
An unauthenticated CometVisu proxy can make openHAB contact internal systems and can return attacker-controlled JavaScript under openHAB’s trusted browser origin. This may expose data or permit unauthorized actions. Remote code execution is described only as a possible outcome when combined with other vulnerabilities.
Executive priority
Remediate immediately where openHAB is reachable from the internet or untrusted networks; treat private deployments as urgent because crafted links can target administrators. Confirm ownership, upgrade completion, and exposure reduction. Investigate suspicious proxy activity, while avoiding claims of compromise without supporting evidence.
Technical view
CometVisu versions 3.4.0.M4 through 4.2.0 expose a proxy endpoint without authentication. Attackers can induce server-side GET requests to otherwise internal resources. They can also proxy malicious content that executes as the CometVisu UI origin, enabling same-origin requests against openHAB. The supplied CVSS 3.1 score is 10.0.
Likely exposure
Affected deployments run the openHAB CometVisu add-on from 3.4.0.M4 through 4.2.0. Internet or other untrusted-network exposure enables direct unauthenticated SSRF. Private deployments may still face browser-based XSS risk if an administrator follows a crafted link.
Exploitation context
The source bundle does not identify this CVE as CISA KEV-listed and provides no evidence of active exploitation. Exploitation requires access to the proxy endpoint for SSRF, or convincing a user to open attacker-supplied content for the described private-network XSS scenario. RCE requires chaining with other vulnerabilities.
Researcher notes
The vulnerability combines unauthenticated SSRF with same-origin script execution through attacker-controlled proxied responses. Scope changes in the supplied CVSS vector, while availability impact is rated none. The bundle maps CWE-918 but does not provide a separate XSS CWE. Patch review should focus on authentication, destination controls, and response handling.
Mitigation direction
Upgrade the CometVisu add-on to version 4.2.1 or later.
Until upgraded, prevent untrusted access to the CometVisu proxy and limit openHAB network exposure.
Restrict unnecessary outbound access from the openHAB host to internal services.
Review the vendor advisory and subsequent openHAB guidance for deployment-specific protections.
Validation and detection
Inventory openHAB installations and identify the installed CometVisu add-on version.
Confirm affected systems have upgraded to CometVisu 4.2.1 or later.
Verify the proxy endpoint is no longer anonymously usable after remediation.
Review access logs for unexpected proxy requests from untrusted sources.
Review network telemetry for unusual outbound GET requests originating from openHAB.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.