CVE-2022-24827

SQL Injection in elide-datastore-aggregation

Workarounds

The vulnerability only exists for parameterized columns of type TEXT and only for analytic queries (CRUD is not impacted). Workarounds include leveraging a different type of parameterized column (TIME, MONEY, etc) or not leveraging parameterized columns.

For more information

If you have any questions or comments about this advisory:

• Open an issue in elide
• Contact us in Discord

When leveraging the following together:

• Elide Aggregation Data Store for Analytic Queries
• Parameterized Columns (A column that requires a client provided parameter)
• A parameterized column of type TEXT

There is the potential for a hacker to provide a carefully crafted query that would bypass server side authorization filters through SQL injection. A recent patch to Elide 6.1.2 allowed the '-' character to be included in parameterized TEXT columns. This character can be interpreted as SQL comments ('--') and allow the attacker to remove the WHERE clause from the generated query and bypass authorization filters.

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.

CVE-2022-24827 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.1.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

A fix is provided in Elide 6.1.4.

1. What is CVE-2022-24827? CVE-2022-24827 is a high-severity SQL injection vulnerability in com.yahoo.elide:elide-datastore-aggregation (maven), affecting versions = 6.1.3. It is fixed in 6.1.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2022-24827? CVE-2022-24827 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.yahoo.elide:elide-datastore-aggregation are affected by CVE-2022-24827? com.yahoo.elide:elide-datastore-aggregation (maven) versions = 6.1.3 is affected.
4. Is there a fix for CVE-2022-24827? Yes. CVE-2022-24827 is fixed in 6.1.4. Upgrade to this version or later.
5. Is CVE-2022-24827 exploitable, and should I be worried? Whether CVE-2022-24827 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
6. What actually determines whether CVE-2022-24827 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.
7. How do I fix CVE-2022-24827? Upgrade com.yahoo.elide:elide-datastore-aggregation to 6.1.4 or later.