GHSA-CGFV-JRFP-2R7V

OpenRemote has Authenticated SQL Injection via Datapoint Crosstab Export

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Kodem intelligence

Already deployed Kodem?

Avoid embedding user-controlled asset names directly into executable SQL.

Recommended options:

1. Do not use asset names as SQL identifiers.

   • Generate deterministic internal column aliases such as c1, c2, c3.
   • Keep the user-facing asset/attribute labels outside SQL and apply them only when serializing CSV headers.

2. If dynamic identifiers are unavoidable, quote them using a database-aware identifier quoting function.

   • For PostgreSQL identifiers, double embedded " characters.
   • Do not perform ad hoc quoting with string concatenation.

3. Avoid fixed dollar-quote delimiters around attacker-influenced content.

   • Use prepared statements or server-side functions where possible.
   • If textual SQL must be generated, choose a delimiter that cannot appear in user input or escape/validate before use.

4. Add a strict validation boundary for display names if the product can tolerate it.

   • This should be defense-in-depth, not the only fix.
   • Reject control characters and SQL-significant delimiter sequences in asset names if they are not required.

5. Add regression tests for:

   • Asset names containing ".
   • Asset names containing the fixed dollar-quote delimiter.
   • Asset names containing newline/comment syntax.
   • Crosstab exports with multiple assets and attributes.
   • Confirmation that returned CSV never contains injected query output.

1. What is GHSA-CGFV-JRFP-2R7V? GHSA-CGFV-JRFP-2R7V is a high-severity SQL injection vulnerability in io.openremote:openremote-manager (maven), affecting versions < 1.26.0. It is fixed in 1.26.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. Which versions of io.openremote:openremote-manager are affected by GHSA-CGFV-JRFP-2R7V? io.openremote:openremote-manager (maven) versions < 1.26.0 is affected.
3. Is there a fix for GHSA-CGFV-JRFP-2R7V? Yes. GHSA-CGFV-JRFP-2R7V is fixed in 1.26.0. Upgrade to this version or later.
4. Is GHSA-CGFV-JRFP-2R7V exploitable, and should I be worried? Whether GHSA-CGFV-JRFP-2R7V is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-CGFV-JRFP-2R7V is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-CGFV-JRFP-2R7V? Upgrade io.openremote:openremote-manager to 1.26.0 or later.

Other vulnerabilities in io.openremote:openremote-manager