GitHub Advisoryadvisory · Packagist

GHSA-ph98-v78f-jqrm SQL injection in jackalope/jackalope-doctrine-dbal

HIGH Published 2021-12-14 Modified 2021-12-14 Official page ↗
Aliases
CVE-2021-43822
Ecosystem
Packagist
Packages
jackalope/jackalope-doctrine-dbal
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Weaknesses
CWE-89
Reviewed
2021-12-14

Affected packages

• Packagist jackalope/jackalope-doctrine-dbal: < 1.7.4 → fixed in 1.7.4

Description

Impact Users can provoke SQL injections if they can specify a node name or query. Patches Upgrade to version 1.7.4 If that is not possible, you can escape all places where `$property` is used to filter `sv:name` in the class `Jackalope\Transport\DoctrineDBAL\Query\QOMWalker`: `XPath::escape($property)`. Workarounds Node names and xpaths can contain `"` or `;` according to the JCR specification. The jackalope component that translates the query object model into doctrine dbal queries does not properly escape the names and paths, so that a accordingly crafted node name can lead to an SQL injection. If queries are never done from user input, or if you validate the user input to not contain `;`, you are not affected. References No further references. For more information If you have any questions or comments about this advisory: • Open an issue in jackalope/jackalope-doctrine-dbal repo

Related

Alias · CVE (1)

  • CVE-2021-43822 Jackalope Doctrine-DBAL is an implementation of the PHP Content Repository API (PHPCR) using a relational database to persist data. vulnerability

Weakness · CWE (1)

  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command weakness

References