SQL Injection in connect-pg-simple
Impact
An unlikely SQL injection if the case of an unsanitized table name input.
Patches
The user should upgrade to 6.0.1. Due to its low impact a backport has not been made to the 5.x branch.
Workarounds
If there is no likelihood that the tableName or schemaName options sent to the constructor could be of an unsanitized nature, then no workaround is needed. Else the input could be sanitized and escaped before sending it in. Take note though that such an escaping would need to be removed when upgrading to 6.0.1 or later, to avoid double escaping.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in voxpelli/node-connect-pg-simple
- Email maintainer at pelle@kodfabrik.se
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | connect-pg-simple | < 6.0.1 | 6.0.1 |
References
- https://github.com/voxpelli/node-connect-pg-simple/security/advisories/GHSA-xqh8-5j36-4556
- https://nvd.nist.gov/vuln/detail/CVE-2019-15658
- https://github.com/advisories/GHSA-xqh8-5j36-4556
- https://github.com/voxpelli/node-connect-pg-simple
- https://snyk.io/vuln/SNYK-JS-CONNECTPGSIMPLE-460154
- https://www.npmjs.com/advisories/1153
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L- Weakness (CWE)
CWE-89- Platform
- npm
- Package
connect-pg-simple- Disclosed
- 26.08.2019
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-xqh8-5j36-4556 - CC BY 4.0
Vulnerability history: connect-pg-simple
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.