Skip to content

SQL injection in jackalope/jackalope-doctrine-dbal

High severity GitHub Reviewed Published Dec 13, 2021 in jackalope/jackalope-doctrine-dbal • Updated Feb 1, 2023

Package

composer jackalope/jackalope-doctrine-dbal (Composer)

Affected versions

< 1.7.4

Patched versions

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:

References

@dbu dbu published to jackalope/jackalope-doctrine-dbal Dec 13, 2021
Published by the National Vulnerability Database Dec 13, 2021
Reviewed Dec 14, 2021
Published to the GitHub Advisory Database Dec 14, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS score

0.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2021-43822

GHSA ID

GHSA-ph98-v78f-jqrm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.