What is CVE-2022-35942?

CVE-2022-35942 is a critical-severity improper input validation vulnerability in loopback-connector-postgresql (npm), affecting versions < 5.5.1. It is fixed in 5.5.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2022-35942?

CVE-2022-35942 has a CVSS score of 9.3 (Critical). 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 loopback-connector-postgresql are affected by CVE-2022-35942?

loopback-connector-postgresql (npm) versions < 5.5.1 is affected.

Is there a fix for CVE-2022-35942?

Yes. CVE-2022-35942 is fixed in 5.5.1. Upgrade to this version or later.

Is CVE-2022-35942 exploitable, and should I be worried?

Whether CVE-2022-35942 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-2022-35942 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-2022-35942?

Upgrade loopback-connector-postgresql to 5.5.1 or later.

CVE-2022-35942 in loopback-connector-postgresql

Q: How severe is CVE-2022-35942?

CVE-2022-35942 has a CVSS score of 9.3 (Critical). 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 loopback-connector-postgresql are affected by CVE-2022-35942?

loopback-connector-postgresql (npm) versions < 5.5.1 is affected.

Q: Is there a fix for CVE-2022-35942?

Yes. CVE-2022-35942 is fixed in 5.5.1. Upgrade to this version or later.

Q: Is CVE-2022-35942 exploitable, and should I be worried?

Whether CVE-2022-35942 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-2022-35942 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-2022-35942?

Upgrade loopback-connector-postgresql to 5.5.1 or later.

Summary

loopback-connector-postgresql Vulnerable to Improper Sanitization of contains Filter

Improper input validation on the contains LoopBack filter may allow for arbitrary SQL injection.

Workarounds

Users who are unable to upgrade should do the following if applicable:

Remove allowExtendedProperties: true DataSource setting
Add allowExtendedProperties: false DataSource setting
When passing directly to the connector functions, manually sanitize the user input for the contains LoopBack filter beforehand.

Impact

When the extended filter property contains is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data stored on the connected database.

This affects users who does any of the following:

Connect to the database via the DataSource with allowExtendedProperties: true setting OR
Uses the connector's CRUD methods directly OR
Uses the connector's other methods to interpret the LoopBack filter.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-35942 has a CVSS score of 9.3 (Critical). The vector is requires local access, no 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 (5.5.1); upgrading removes the vulnerable code path.

Affected versions

loopback-connector-postgresql (< 5.5.1)

Security releases

loopback-connector-postgresql → 5.5.1 (npm)

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

Patch release [email protected] has been published of which resolves this issue.

Frequently Asked Questions

What is CVE-2022-35942? CVE-2022-35942 is a critical-severity improper input validation vulnerability in loopback-connector-postgresql (npm), affecting versions < 5.5.1. It is fixed in 5.5.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2022-35942? CVE-2022-35942 has a CVSS score of 9.3 (Critical). 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 loopback-connector-postgresql are affected by CVE-2022-35942? loopback-connector-postgresql (npm) versions < 5.5.1 is affected.
Is there a fix for CVE-2022-35942? Yes. CVE-2022-35942 is fixed in 5.5.1. Upgrade to this version or later.
Is CVE-2022-35942 exploitable, and should I be worried? Whether CVE-2022-35942 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-2022-35942 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-2022-35942? Upgrade loopback-connector-postgresql to 5.5.1 or later.