Categories
CVE-2024-42467 critical CVSS 10.0

SSRF (Server-Side Request Forgery) in org.openhab.ui.bundles:org.openhab.ui.cometvisu (CVE-2024-42467)

Summary

SSRF in org.openhab.ui.bundles:org.openhab.ui.cometvisu (CVE-2024-42467). Confidential information can be exposed externally. Mitigation: upgrade to 4.2.1 or later.

Original description

The description as published by the source.

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 vulnerability was discovered with the help of CodeQL's Server-side request forgery query.

Impact

This issue may lead up to Remote Code Execution (RCE) when chained with other vulnerabilities (see: GHSL-2024-007).

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-42467 has been found in org.openhab.ui.bundles:org.openhab.ui.cometvisu.
Confidential information can be exposed externally. CVSS score: 10.0/10.
What to do: upgrade org.openhab.ui.bundles:org.openhab.ui.cometvisu to 4.2.1 or later.
If unsure, ask your IT team or search "org.openhab.ui.bundles:org.openhab.ui.cometvisu CVE-2024-42467" on the vendor's site.

CVE-2024-42467 (org.openhab.ui.bundles:org.openhab.ui.cometvisu) — CWE-918 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in org.openhab.ui.bundles:org.openhab.ui.cometvisu.

📍 Affected scope

Check the vendor advisory for the affected versions of org.openhab.ui.bundles:org.openhab.ui.cometvisu.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.openhab.ui.bundles:org.openhab.ui.cometvisu を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.openhab.ui.bundles:org.openhab.ui.cometvisu to 4.2.1

    ステージング環境で 4.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.openhab.ui.bundles:org.openhab.ui.cometvisu
[{"type":"ECOSYSTEM","events":[{"introduced":"3.4.0.M4"},{"fixed":"4.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details