Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency pg-native to v3 [security] #62

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 25, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pg-native ^1.10.0 -> ^3.0.1 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-25852

pg-native before 3.0.1 and libpq before 1.8.10 are vulnerable to Denial of Service (DoS) when the addons attempt to cast the second argument to an array and fail. This happens for every non-array argument passed. Note: pg-native is a mere binding to npm's libpq library, which in turn has the addons and bindings to the actual C libpq library. This means that problems found in pg-native may transitively impact npm's libpq.


Release Notes

brianc/node-pg-native (pg-native)

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.2.0

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

v1.10.1

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from c53f6f3 to 87ae231 Compare March 25, 2023 03:07
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from ac72053 to e1eff43 Compare April 3, 2023 11:37
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from fb74184 to 383f176 Compare April 17, 2023 16:16
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 3 times, most recently from 5edf111 to 270a4fa Compare June 4, 2023 08:16
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from 270a4fa to 82f2088 Compare June 4, 2023 15:26
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 6 times, most recently from 1fc5de5 to 5cd4ab5 Compare June 19, 2023 11:34
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 36c8969 to 40eb432 Compare June 29, 2023 13:40
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from 93828f5 to 3c1c515 Compare July 9, 2023 12:21
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from 8f0b554 to 9739b42 Compare July 19, 2023 17:33
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from d66f986 to efd1875 Compare August 1, 2023 18:13
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from efd1875 to 15d47b4 Compare August 9, 2023 14:56
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 3 times, most recently from 0bddfea to 8f28149 Compare February 4, 2024 12:12
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from 7dea183 to 77184d2 Compare February 29, 2024 13:20
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from 2f35085 to da7db3e Compare March 17, 2024 09:29
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from b4cca36 to 98ed407 Compare March 24, 2024 16:20
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 18c9d73 to 9d46c17 Compare April 14, 2024 10:58
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from d954717 to eb9216c Compare April 25, 2024 13:15
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from 47c847f to 6296675 Compare May 9, 2024 13:45
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 22680d1 to 7357027 Compare May 16, 2024 02:41
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from 7357027 to fcade9a Compare June 4, 2024 14:26
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from fcade9a to 0e4bb19 Compare June 4, 2024 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants