What is CVE-2019-15658?

CVE-2019-15658 is a high-severity SQL injection vulnerability in connect-pg-simple (npm), affecting versions < 6.0.1. It is fixed in 6.0.1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2019-15658?

CVE-2019-15658 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of connect-pg-simple are affected by CVE-2019-15658?

connect-pg-simple (npm) versions < 6.0.1 is affected.

Is there a fix for CVE-2019-15658?

Yes. CVE-2019-15658 is fixed in 6.0.1. Upgrade to this version or later.

Is CVE-2019-15658 exploitable, and should I be worried?

Whether CVE-2019-15658 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-15658 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2019-15658?

Upgrade connect-pg-simple to 6.0.1 or later.

CVE-2019-15658 in connect-pg-simple

Q: How severe is CVE-2019-15658?

CVE-2019-15658 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of connect-pg-simple are affected by CVE-2019-15658?

connect-pg-simple (npm) versions < 6.0.1 is affected.

Q: Is there a fix for CVE-2019-15658?

Yes. CVE-2019-15658 is fixed in 6.0.1. Upgrade to this version or later.

Q: Is CVE-2019-15658 exploitable, and should I be worried?

Whether CVE-2019-15658 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-15658 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-15658?

Upgrade connect-pg-simple to 6.0.1 or later.

Summary

SQL Injection in connect-pg-simple

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

Security issue disclosure

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 [email protected]

Impact

An unlikely SQL injection if the case of an unsanitized table name input.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2019-15658 has a CVSS score of 7.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.0.1); upgrading removes the vulnerable code path.

Affected versions

connect-pg-simple (< 6.0.1)

Security releases

connect-pg-simple → 6.0.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The user should upgrade to 6.0.1. Due to its low impact a backport has not been made to the 5.x branch.

Frequently Asked Questions

What is CVE-2019-15658? CVE-2019-15658 is a high-severity SQL injection vulnerability in connect-pg-simple (npm), affecting versions < 6.0.1. It is fixed in 6.0.1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2019-15658? CVE-2019-15658 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of connect-pg-simple are affected by CVE-2019-15658? connect-pg-simple (npm) versions < 6.0.1 is affected.
Is there a fix for CVE-2019-15658? Yes. CVE-2019-15658 is fixed in 6.0.1. Upgrade to this version or later.
Is CVE-2019-15658 exploitable, and should I be worried? Whether CVE-2019-15658 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-15658 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-15658? Upgrade connect-pg-simple to 6.0.1 or later.