GHSA-8XPJ-9J9G-FC9R

Vulnerability from github – Published: 2022-04-08 22:43 – Updated: 2022-04-18 22:19
VLAI
Summary
SQL Injection in elide-datastore-aggregation
Details

Impact

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.

Patches

A fix is provided in Elide 6.1.4.

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.yahoo.elide:elide-datastore-aggregation"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.1.3"
            },
            {
              "fixed": "6.1.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "6.1.3"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-24827"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-04-08T22:43:17Z",
    "nvd_published_at": "2022-04-11T21:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\nWhen leveraging the following together:\n\n- Elide Aggregation Data Store for Analytic Queries\n- Parameterized Columns (A column that requires a client provided parameter)\n- A parameterized column of type TEXT\n\nThere 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 \u0027-\u0027 character to be included in parameterized TEXT columns.  This character can be interpreted as SQL comments (\u0027--\u0027) and allow the attacker to remove the WHERE clause from the generated query and bypass authorization filters.\n\n### Patches\nA [fix](https://github.com/yahoo/elide/pull/2581) is provided in [Elide 6.1.4](https://github.com/yahoo/elide/releases/tag/6.1.4).\n\n### Workarounds\nThe 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [elide](https://github.com/yahoo/elide)\n* Contact us in [Discord](https://discord.com/invite/3vh8ac57cc)\n",
  "id": "GHSA-8xpj-9j9g-fc9r",
  "modified": "2022-04-18T22:19:44Z",
  "published": "2022-04-08T22:43:17Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/yahoo/elide/security/advisories/GHSA-8xpj-9j9g-fc9r"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-24827"
    },
    {
      "type": "WEB",
      "url": "https://github.com/yahoo/elide/pull/2581"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/yahoo/elide"
    },
    {
      "type": "WEB",
      "url": "https://github.com/yahoo/elide/releases/tag/6.1.4"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "SQL Injection in elide-datastore-aggregation"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.