Merged
Conversation
Fixes 2786
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2786
Pull requests for reference:
brianc/node-pg-native#108
brianc/node-libpq#86
This shouldn't actually affect anything in this library as there's no way to get an array into the offending parameters variable in node-libpq from this library directly anyway AFAICT, but still...I take any security issue extremely seriously (and even stopped working today to fix this). Please LMK if there are other issues related to this.
A note for anyone on how to upgrade:
You technically don't even need to install a new version of
pg. Just make sure you installpg-native@3.0.1if you're using the native bindings. e.g.yarn add pg-native@3.0.1etc...