← Back
GHSA-cgfv-jrfp-2r7v

SQL Injection in io.openremote:openremote-manager (GHSA-cgfv-jrfp-2r7v)

Summary

SQL injection in io.openremote:openremote-manager (GHSA-cgfv-jrfp-2r7v). Risk of unauthorized operations or information disclosure. Exploitable via ``SELECT``. Mitigation: upgrade to `1.26.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **GHSA-cgfv-jrfp-2r7v** has been found in io.openremote:openremote-manager. Attackers can target a specific entry point like ``SELECT`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade io.openremote:openremote-manager to **1.26.0** or later. If unsure, ask your IT team or search "io.openremote:openremote-manager GHSA-cgfv-jrfp-2r7v" on the vendor's site.
GHSA-cgfv-jrfp-2r7v (io.openremote:openremote-manager) — CWE-89 / Attack surface: `SELECT` / `COPY` / `current_user` / `col_0` Patched: `1.26.0` — 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
**SQL injection** (CWE-89) exists in io.openremote:openremote-manager. Attackers reach the vulnerable code path via ``SELECT`` without authentication.
📍 Affected scope
io.openremote:openremote-manager — . Attack surface: `SELECT` / `COPY` / `current_user` / `col_0`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.26.0**.
🛡️ 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. Run `grep -r 'io.openremote:openremote-manager' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

  1. 1
    Identify exposure identify
    grep -r 'io.openremote:openremote-manager' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.openremote:openremote-manager` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade io.openremote:openremote-manager to 1.26.0

    ステージング環境で 1.26.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

maven io.openremote:openremote-manager
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →