What is CVE-2021-43822?

CVE-2021-43822 is a high-severity SQL injection vulnerability in jackalope/jackalope-doctrine-dbal (composer), affecting versions < 1.7.4. It is fixed in 1.7.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2021-43822?

CVE-2021-43822 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of jackalope/jackalope-doctrine-dbal are affected by CVE-2021-43822?

jackalope/jackalope-doctrine-dbal (composer) versions < 1.7.4 is affected.

Is there a fix for CVE-2021-43822?

Yes. CVE-2021-43822 is fixed in 1.7.4. Upgrade to this version or later.

Is CVE-2021-43822 exploitable, and should I be worried?

Whether CVE-2021-43822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2021-43822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2021-43822 in jackalope/jackalope-doctrine-dbal

Q: How severe is CVE-2021-43822?

CVE-2021-43822 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of jackalope/jackalope-doctrine-dbal are affected by CVE-2021-43822?

jackalope/jackalope-doctrine-dbal (composer) versions < 1.7.4 is affected.

Q: Is there a fix for CVE-2021-43822?

Yes. CVE-2021-43822 is fixed in 1.7.4. Upgrade to this version or later.

Q: Is CVE-2021-43822 exploitable, and should I be worried?

Whether CVE-2021-43822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2021-43822 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2021-43822?

Upgrade jackalope/jackalope-doctrine-dbal to 1.7.4 or later.

Summary

SQL injection in jackalope/jackalope-doctrine-dbal

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

Impact

Users can provoke SQL injections if they can specify a node name or query.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2021-43822 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.4); upgrading removes the vulnerable code path.

Affected versions

jackalope/jackalope-doctrine-dbal (< 1.7.4)

Security releases

jackalope/jackalope-doctrine-dbal → 1.7.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade jackalope/jackalope-doctrine-dbal to 1.7.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2021-43822? CVE-2021-43822 is a high-severity SQL injection vulnerability in jackalope/jackalope-doctrine-dbal (composer), affecting versions < 1.7.4. It is fixed in 1.7.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2021-43822? CVE-2021-43822 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of jackalope/jackalope-doctrine-dbal are affected by CVE-2021-43822? jackalope/jackalope-doctrine-dbal (composer) versions < 1.7.4 is affected.
Is there a fix for CVE-2021-43822? Yes. CVE-2021-43822 is fixed in 1.7.4. Upgrade to this version or later.
Is CVE-2021-43822 exploitable, and should I be worried? Whether CVE-2021-43822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2021-43822 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2021-43822? Upgrade jackalope/jackalope-doctrine-dbal to 1.7.4 or later.