GMS-2022-3552: Duplicate of ./npm/loopback-connector-postgresql/CVE-2022-35942.yml
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: truesetting 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: trueDataSource setting - Add
allowExtendedProperties: falseDataSource setting - When passing directly to the connector functions, manually sanitize the user input for the
containsLoopBack filter beforehand.
References
Code Behaviors & Features
Detect and mitigate GMS-2022-3552 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →