Vulnerability Details CVE-2017-16082
A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name. There are 2 likely scenarios in which one would likely be vulnerable. 1) Executing unsafe, user-supplied sql which contains a malicious column name. 2) Connecting to an untrusted database and executing a query which returns results where any of the column names are malicious.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.716
EPSS Ranking 98.6%
CVSS Severity
CVSS v3 Score 9.8
CVSS v2 Score 7.5
References
Products affected by CVE-2017-16082
-
cpe:2.3:a:node-postgres:pg:2.0.0
-
cpe:2.3:a:node-postgres:pg:2.1.0
-
cpe:2.3:a:node-postgres:pg:2.10.0
-
cpe:2.3:a:node-postgres:pg:2.11.0
-
cpe:2.3:a:node-postgres:pg:2.11.1
-
cpe:2.3:a:node-postgres:pg:2.2.0
-
cpe:2.3:a:node-postgres:pg:2.3.0
-
cpe:2.3:a:node-postgres:pg:2.3.1
-
cpe:2.3:a:node-postgres:pg:2.4.0
-
cpe:2.3:a:node-postgres:pg:2.5.0
-
cpe:2.3:a:node-postgres:pg:2.5.1
-
cpe:2.3:a:node-postgres:pg:2.6.0
-
cpe:2.3:a:node-postgres:pg:2.6.1
-
cpe:2.3:a:node-postgres:pg:2.6.2
-
cpe:2.3:a:node-postgres:pg:2.7.0
-
cpe:2.3:a:node-postgres:pg:2.8.0
-
cpe:2.3:a:node-postgres:pg:2.8.1
-
cpe:2.3:a:node-postgres:pg:2.8.2
-
cpe:2.3:a:node-postgres:pg:2.8.3
-
cpe:2.3:a:node-postgres:pg:2.8.4
-
cpe:2.3:a:node-postgres:pg:2.8.5
-
cpe:2.3:a:node-postgres:pg:2.9.0
-
cpe:2.3:a:node-postgres:pg:3.0.0
-
cpe:2.3:a:node-postgres:pg:3.0.2
-
cpe:2.3:a:node-postgres:pg:3.0.3
-
cpe:2.3:a:node-postgres:pg:3.1.0
-
cpe:2.3:a:node-postgres:pg:3.2.0
-
cpe:2.3:a:node-postgres:pg:3.3.0
-
cpe:2.3:a:node-postgres:pg:3.4.0
-
cpe:2.3:a:node-postgres:pg:3.4.1
-
cpe:2.3:a:node-postgres:pg:3.4.2
-
cpe:2.3:a:node-postgres:pg:3.4.3
-
cpe:2.3:a:node-postgres:pg:3.4.4
-
cpe:2.3:a:node-postgres:pg:3.4.5
-
cpe:2.3:a:node-postgres:pg:3.5.0
-
cpe:2.3:a:node-postgres:pg:3.6.0
-
cpe:2.3:a:node-postgres:pg:3.6.1
-
cpe:2.3:a:node-postgres:pg:3.6.2
-
cpe:2.3:a:node-postgres:pg:3.6.3
-
cpe:2.3:a:node-postgres:pg:4.0.0
-
cpe:2.3:a:node-postgres:pg:4.1.0
-
cpe:2.3:a:node-postgres:pg:4.1.1
-
cpe:2.3:a:node-postgres:pg:4.2.0
-
cpe:2.3:a:node-postgres:pg:4.3.0
-
cpe:2.3:a:node-postgres:pg:4.4.0
-
cpe:2.3:a:node-postgres:pg:4.4.1
-
cpe:2.3:a:node-postgres:pg:4.4.2
-
cpe:2.3:a:node-postgres:pg:4.4.3
-
cpe:2.3:a:node-postgres:pg:4.4.4
-
cpe:2.3:a:node-postgres:pg:4.4.5
-
cpe:2.3:a:node-postgres:pg:4.4.6
-
cpe:2.3:a:node-postgres:pg:4.5.0
-
cpe:2.3:a:node-postgres:pg:4.5.1
-
cpe:2.3:a:node-postgres:pg:4.5.2
-
cpe:2.3:a:node-postgres:pg:4.5.3
-
cpe:2.3:a:node-postgres:pg:4.5.4
-
cpe:2.3:a:node-postgres:pg:4.5.5
-
cpe:2.3:a:node-postgres:pg:4.5.6
-
cpe:2.3:a:node-postgres:pg:5.1.0
-
cpe:2.3:a:node-postgres:pg:6.0.0
-
cpe:2.3:a:node-postgres:pg:6.0.1
-
cpe:2.3:a:node-postgres:pg:6.0.2
-
cpe:2.3:a:node-postgres:pg:6.0.3
-
cpe:2.3:a:node-postgres:pg:6.0.4
-
cpe:2.3:a:node-postgres:pg:6.0.5
-
cpe:2.3:a:node-postgres:pg:6.1.0
-
cpe:2.3:a:node-postgres:pg:6.1.1
-
cpe:2.3:a:node-postgres:pg:6.1.2
-
cpe:2.3:a:node-postgres:pg:6.1.3
-
cpe:2.3:a:node-postgres:pg:6.1.4
-
cpe:2.3:a:node-postgres:pg:6.1.5
-
cpe:2.3:a:node-postgres:pg:6.1.6
-
cpe:2.3:a:node-postgres:pg:6.2.2
-
cpe:2.3:a:node-postgres:pg:6.2.3
-
cpe:2.3:a:node-postgres:pg:6.2.4
-
cpe:2.3:a:node-postgres:pg:6.2.5
-
cpe:2.3:a:node-postgres:pg:6.3.0
-
cpe:2.3:a:node-postgres:pg:6.3.1
-
cpe:2.3:a:node-postgres:pg:6.3.3
-
cpe:2.3:a:node-postgres:pg:6.4.0
-
cpe:2.3:a:node-postgres:pg:6.4.1
-
cpe:2.3:a:node-postgres:pg:7.0.0
-
cpe:2.3:a:node-postgres:pg:7.0.1
-
cpe:2.3:a:node-postgres:pg:7.0.2
-
cpe:2.3:a:node-postgres:pg:7.0.3
-
cpe:2.3:a:node-postgres:pg:7.1.0
-
cpe:2.3:a:node-postgres:pg:7.1.1