Skip to content

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

Critical severity GitHub Reviewed Published Aug 9, 2022 in loopbackio/loopback-connector-postgresql • Updated Jan 27, 2023

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.

References

@achrinza achrinza published to loopbackio/loopback-connector-postgresql Aug 9, 2022
Published to the GitHub Advisory Database Aug 11, 2022
Reviewed Aug 11, 2022
Published by the National Vulnerability Database Aug 12, 2022
Last updated Jan 27, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

0.180%
(56th percentile)

Weaknesses

CVE ID

CVE-2022-35942

GHSA ID

GHSA-j259-6c58-9m58

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.