Categories
CVE-2021-43822

SQL Injection in jackalope/jackalope-doctrine-dbal (CVE-2021-43822)

Summary

SQL injection in jackalope/jackalope-doctrine-dbal (CVE-2021-43822). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.7.4 or later.

Original description

The description as published by the source.

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:

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-43822 has been found in jackalope/jackalope-doctrine-dbal.
Successful exploitation can lead to full system takeover.
What to do: upgrade jackalope/jackalope-doctrine-dbal to 1.7.4 or later.
If unsure, ask your IT team or search "jackalope/jackalope-doctrine-dbal CVE-2021-43822" on the vendor's site.

CVE-2021-43822 (jackalope/jackalope-doctrine-dbal) — CWE-89
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.7.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in jackalope/jackalope-doctrine-dbal.

📍 Affected scope

Check the vendor advisory for the affected versions of jackalope/jackalope-doctrine-dbal.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.7.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jackalope/jackalope-doctrine-dbal' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'jackalope/jackalope-doctrine-dbal' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jackalope/jackalope-doctrine-dbal を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade jackalope/jackalope-doctrine-dbal to 1.7.4

    ステージング環境で 1.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist jackalope/jackalope-doctrine-dbal
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details