Jackalope Doctrine Dbal
Approved changes feed: RSS · Atom
cpe:2.3:a:jackalope:jackalope-doctrine-dbal:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Jackalope (abac62ed-f6dd-5419-b8f1-ac6e9f84b1d4) |
|---|---|
| Product | Jackalope Doctrine Dbal (09c64b2b-a419-54b2-8bd7-58a1d378023a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-43822 |
vulnerable | 2026-06-08 05:36:44.375522 |
SQL injection in jackalope/jackalope-doctrine-dbal
HIGH (8.5)
Jackalope Doctrine-DBAL is an implementation of the PHP Content Repository API (PHPCR) using a relational database to persist data. In affected versions users can provoke SQL injections if they can specify a node name or query. Upgrade to version 1.7.4 to resolve this issue. 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)`. 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.
Published: 2021-12-13T19:50:11.000Z
Updated: 2024-08-04T04:03:08.861Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.