Skip to content

Improper Sanitization of `contains` Filter

Critical
achrinza published GHSA-j259-6c58-9m58 Aug 9, 2022

Package

npm loopback-connector-postgresql (npm)

Affected versions

< 5.5.1

Patched versions

5.5.1

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 loopback-connector-postgresql@5.5.1 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.

For more information

If there are additional security issues with the LoopBack project, please report them to security@loopback.io using the LoopBack Security Team Email PGP key.

Severity

Critical
9.3
/ 10

CVSS base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CVE ID

CVE-2022-35942

Credits