dbcve.org
Openhab Web InterfaceApplication · Openhab

CVE-2024-42467

CRITICAL · 10.0 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 4.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CometVisu add-on in openHAB exposes an unauthenticated proxy endpoint prior to version 4.2.1. This proxy can be exploited for Server-Side Request Forgery (SSRF) to make GET requests to internal-only services, and for Cross-Site Scripting (XSS) by redirecting requests through an attacker-controlled server that returns malicious JavaScript executing with the CometVisu UI origin.

MitigationUpgrade the CometVisu add-on to version 4.2.1 or later to patch the authentication bypass. Additionally, ensure openHAB is not exposed to untrusted networks to mitigate SSRF risks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openhab Web InterfaceApplication
Affected:< 4.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CometVisu add-on version
    In the openHAB main UI, navigate to Settings > Add-ons > Bindings, locate the CometVisu add-on, and note the installed version number. Alternatively, check the Karaf console with the command 'bundle:list | grep -i cometvisu' to view the installed bundle version.
    Affected if The displayed version is earlier than 4.2.1, or the bundle is present but version information cannot be determined (treat as potentially vulnerable).
  2. Confirm CometVisu is enabled
    In openHAB UI, verify that the CometVisu binding is installed and the CometVisu UI is accessible via the sidebar or direct URL (typically /cometvisu/). Check that the CometVisu runtime service is active in the Karaf console with 'bundle:list | grep -i cometvisu' showing state ACTIVE.
    Affected if CometVisu is installed and active with a version below 4.2.1.
  3. Check openHAB network binding
    Inspect the openHAB configuration file 'userdata/etc/org.ops4j.pax.web.cfg' or the main configuration, looking for the 'org.ops4j.pax.web.cfg' setting 'org.ops4j.pax.web.cfg' or similar that defines the HTTP service bind address. Run command 'netstat -tlnp | grep 8080' or 'ss -tlnp | grep 8080' to see which interface openHAB is listening on.
    Affected if openHAB is bound to 0.0.0.0 or an externally accessible IP address, making the proxy endpoint reachable from untrusted networks.

You are affected if the CometVisu add-on is installed with a version below 4.2.1 and openHAB is network-accessible (even internally), as the unauthenticated proxy endpoint can be exploited for SSRF or XSS attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.1 or later
Fixed in 4.2.1
Vendor patch github.com →
Interim mitigation

Upgrade the CometVisu add-on to version 4.2.1 or later to patch the authentication bypass. Additionally, ensure openHAB is not exposed to untrusted networks to mitigate SSRF risks.

Recommended fix High confidence

CometVisu add-on version 4.2.1

  1. Upgrade the CometVisu add-on to version 4.2.1 or later to patch the vulnerability
  2. Ensure the openHAB instance is updated to include the patched CometVisu add-on

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openhab Web Interface Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42467 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data