~ / search / GHSA-ph98-v78f-jqrm

GHSA-ph98-v78f-jqrm

SQL injection in jackalope/jackalope-doctrine-dbal

Source: GitHub Advisory Database (reviewed) High CVE-2021-43822

Packages

EcosystemPackageAffectedFixed in
Packagist jackalope/jackalope-doctrine-dbal < 1.7.4 1.7.4

Details

As written in the advisory (Markdown source, shown as plain text).

### 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](https://github.com/jackalope/jackalope-doctrine-dbal/issues)

References

External links from the advisory. They lead to third-party sites.