# CVE-2017-16082: Remote Code Execution in pg > Remote code execution in the pg Node.js module via crafted column names from untrusted databases or unsafe SQL queries. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Jun 2018 - **Updated:** 17 Sep 2024 - **Also known as:** DEBIAN-CVE-2017-16082, GHSA-wc9v-mj63-m9g5, UBUNTU-CVE-2017-16082 ## What is CVE-2017-16082? CVE-2017-16082 is a critical code injection vulnerability in HackerOne pg node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2017-16082? 22 open source packages ship an affected version, including pg. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pg` | npm | All versions | 2.11.2 | | `pg` | npm | All versions | 2.11.2 | | `pg` | npm | From 3.0.0 | 3.6.4 | | `pg` | npm | From 3.0.0 | 3.6.4 | | `pg` | npm | From 4.0.0 | 4.5.7 | | `pg` | npm | From 4.0.0 | 4.5.7 | | `pg` | npm | From 5.0.0 | 5.2.1 | | `pg` | npm | From 5.0.0 | 5.2.1 | | `pg` | npm | From 6.0.0 | 6.0.5 | | `pg` | npm | From 6.0.0 | 6.0.5 | | `pg` | npm | From 6.1.0 | 6.1.6 | | `pg` | npm | From 6.1.0 | 6.1.6 | | `pg` | npm | From 6.2.0 | 6.2.5 | | `pg` | npm | From 6.2.0 | 6.2.5 | | `pg` | npm | From 6.3.0 | 6.3.3 | | `pg` | npm | From 6.3.0 | 6.3.3 | | `pg` | npm | From 6.4.0 | 6.4.2 | | `pg` | npm | From 6.4.0 | 6.4.2 | | `pg` | npm | From 7.0.0 | 7.0.2 | | `pg` | npm | From 7.0.0 | 7.0.2 | | `pg` | npm | From 7.1.0 | 7.1.2 | | `pg` | npm | From 7.1.0 | 7.1.2 | Products: Node-Postgres Pg. ## How do I fix CVE-2017-16082? Upgrade pg to a fixed version for your release line: 2.11.2, 3.6.4, 4.5.7 or 5.2.1. ## Is CVE-2017-16082 being exploited? There is no known exploitation of CVE-2017-16082 in the wild and no public exploit code. Public exploit code: - NodeJS + Postgres (Remote Code Execution) 🛰 (github_poc): https://github.com/nulldreams/CVE-2017-16082 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-16082 and fix it if it is affected. What it is: CVE-2017-16082 is a critical code injection vulnerability in HackerOne pg node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-16082 in the wild and no public exploit code. Affected packages and fixed versions: - pg (npm): affected all versions; fixed in 2.11.2 - pg (npm): affected all versions; fixed in 2.11.2 - pg (npm): affected from 3.0.0; fixed in 3.6.4 - pg (npm): affected from 3.0.0; fixed in 3.6.4 - pg (npm): affected from 4.0.0; fixed in 4.5.7 - pg (npm): affected from 4.0.0; fixed in 4.5.7 - pg (npm): affected from 5.0.0; fixed in 5.2.1 - pg (npm): affected from 5.0.0; fixed in 5.2.1 - pg (npm): affected from 6.0.0; fixed in 6.0.5 - pg (npm): affected from 6.0.0; fixed in 6.0.5 - pg (npm): affected from 6.1.0; fixed in 6.1.6 - pg (npm): affected from 6.1.0; fixed in 6.1.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-16082/ (Markdown: https://insights.sbomify.com/CVE-2017-16082/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16082 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16082 - OSV: https://osv.dev/vulnerability/CVE-2017-16082 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-16082/ Summaries are generated and may contain mistakes; the official description above is the record.