CVE-2022-35942

Description

Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. ### 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. ### Patches Patch release `[email protected]` has been published of which resolves this issue. ### 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.

How to fix CVE-2022-35942

To remediate CVE-2022-35942, upgrade the affected package to a fixed version below.

• —upgrade to 5.5.1 or later

Is CVE-2022-35942 being exploited?

Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 5.5.1

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2022-35942
• WEBgithub.com/loopbackio/loopback-connector-postgresql
• WEBgithub.com/loopbackio/loopback-connector-postgresql/commit/d57406c6737692a3a106b58a35406290cddb23e5
• WEBgithub.com/loopbackio/loopback-connector-postgresql/security/advisories/GHSA-j259-6c58-9m58