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.
| Package (Ecosystem) | Introduced | Fixed | Limit |
|---|---|---|---|
| pg(npm) | 0 | 2.11.2 | N/A |
| pg(npm) | 3.0.0 | 3.6.4 | N/A |
| pg(npm) | 4.0.0 | 4.5.7 | N/A |
| pg(npm) | 5.0.0 | 5.2.1 | N/A |
| pg(npm) | 6.0.0 | 6.0.5 | N/A |
| pg(npm) | 6.1.0 | 6.1.6 | N/A |
| pg(npm) | 6.2.0 | 6.2.5 | N/A |
| pg(npm) | 6.3.0 | 6.3.3 | N/A |
| pg(npm) | 6.4.0 | 6.4.2 | N/A |
| pg(npm) | 7.0.0 | 7.0.2 | N/A |
| pg(npm) | 7.1.0 | 7.1.2 | N/A |
CVSS Metrics
