For your digest
pg: Remote Code Execution in pg
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
pg (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- pg (npm): every version, before 2.11.2
- pg (npm): from 3.0.0, before 3.6.4
- pg (npm): from 4.0.0, before 4.5.7
- pg (npm): from 5.0.0, before 5.2.1
- pg (npm): from 6.0.0, before 6.0.5
- pg (npm): from 6.1.0, before 6.1.6
- pg (npm): from 6.2.0, before 6.2.5
- pg (npm): from 6.3.0, before 6.3.3
- pg (npm): from 6.4.0, before 6.4.2
- pg (npm): from 7.0.0, before 7.0.2
- pg (npm): from 7.1.0, before 7.1.2
The fix
pg (npm) fixed in 2.11.2
npmnpm install pg@2.11.2pnpmpnpm add pg@2.11.2yarnyarn add pg@2.11.2bunbun add pg@2.11.2Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 2.11.2 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 3.6.4
npmnpm install pg@3.6.4pnpmpnpm add pg@3.6.4yarnyarn add pg@3.6.4bunbun add pg@3.6.4Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 3.6.4 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 4.5.7
npmnpm install pg@4.5.7pnpmpnpm add pg@4.5.7yarnyarn add pg@4.5.7bunbun add pg@4.5.7Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 4.5.7 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 5.2.1
npmnpm install pg@5.2.1pnpmpnpm add pg@5.2.1yarnyarn add pg@5.2.1bunbun add pg@5.2.1Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 5.2.1 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 6.0.5
npmnpm install pg@6.0.5pnpmpnpm add pg@6.0.5yarnyarn add pg@6.0.5bunbun add pg@6.0.5Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 6.0.5 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 6.1.6
npmnpm install pg@6.1.6pnpmpnpm add pg@6.1.6yarnyarn add pg@6.1.6bunbun add pg@6.1.6Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 6.1.6 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 6.2.5
npmnpm install pg@6.2.5pnpmpnpm add pg@6.2.5yarnyarn add pg@6.2.5bunbun add pg@6.2.5Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 6.2.5 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 6.3.3
npmnpm install pg@6.3.3pnpmpnpm add pg@6.3.3yarnyarn add pg@6.3.3bunbun add pg@6.3.3Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 6.3.3 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 6.4.2
npmnpm install pg@6.4.2pnpmpnpm add pg@6.4.2yarnyarn add pg@6.4.2bunbun add pg@6.4.2Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 6.4.2 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 7.0.2
npmnpm install pg@7.0.2pnpmpnpm add pg@7.0.2yarnyarn add pg@7.0.2bunbun add pg@7.0.2Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 7.0.2 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.pg (npm) fixed in 7.1.2
npmnpm install pg@7.1.2pnpmpnpm add pg@7.1.2yarnyarn add pg@7.1.2bunbun add pg@7.1.2Check what is installednpm ls pgPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency pg to 7.1.2 or the nearest later release, to fix CVE-2017-16082. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".