Skip to content

Comments

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

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-pg-native-vulnerability
Open

fix(deps): update dependency pg-native to v3 [security]#62
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-pg-native-vulnerability

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 25, 2022

This PR contains the following updates:

Package Change Age Confidence
pg-native (source) ^1.10.0^3.0.1 age 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-postgres (pg-native)

v3.0.1

Compare Source

v3.0.0

Compare Source

  • Rewrote stream internals to better conform to node stream semantics. This should make pg-query-stream much better at respecting highWaterMark and getting rid of some edge case bugs when using pg-query-stream as an async iterator. Due to the size and nature of this change (effectively a full re-write) it's safest to bump the semver major here, though almost all tests remain untouched and still passing, which brings us to a breaking change to the API....
  • Changed stream.close to stream.destroy which is the official way to terminate a readable stream. This is a breaking change if you rely on the stream.close method on pg-query-stream...though should be just a find/replace type operation to upgrade as the semantics remain very similar (not exactly the same, since internals are rewritten, but more in line with how streams are "supposed" to behave).
  • Unified the config.batchSize and config.highWaterMark to both do the same thing: control how many rows are buffered in memory. The ReadableStream will manage exactly how many rows are requested from the cursor at a time. This should give better out of the box performance and help with efficient async iteration.

v2.2.0

Compare Source

  • Switch internal protocol parser & serializer to pg-protocol. The change is backwards compatible but results in a significant performance improvement across the board, with some queries as much as 50% faster.

v2.0.1

Compare Source

v2.0.0

Compare Source

  • Properly handle various PostgreSQL to JavaScript type conversions to avoid data loss:
PostgreSQL | pg@v2.0 JavaScript | pg@v1.0 JavaScript
--------------------------------|----------------
float4     | number (float)     | string
float8     | number (float)     | string
int8       | string             | number (int)
numeric    | string             | number (float)
decimal    | string             | number (float)

For more information see #​353
If you are unhappy with these changes you can always override the built in type parsing fairly easily.

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 was generated by Mend Renovate. View the repository job log.

@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 from b70ce5a to 484af54 Compare August 31, 2025 13:23
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 1393827 to ff28027 Compare September 25, 2025 22:02
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 5629018 to 97e7ad8 Compare October 22, 2025 00:51
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 433d5d7 to 6c387cd Compare November 11, 2025 04:07
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 46e0966 to 69b3f2a Compare November 19, 2025 00:06
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 3 times, most recently from bd4ca84 to d1c58db Compare December 10, 2025 12:30
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from d1c58db to 2907604 Compare December 10, 2025 20:04
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 4 times, most recently from d0d33f8 to 2f580cf Compare December 31, 2025 19:31
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 799fa19 to 5539855 Compare January 8, 2026 23:07
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 3a4d3d4 to 38c6d5c Compare January 19, 2026 21:27
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 2 times, most recently from 089e036 to df2111b Compare February 3, 2026 02:09
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch 5 times, most recently from a546054 to 6fc374e Compare February 17, 2026 19:36
@renovate renovate bot force-pushed the renovate/npm-pg-native-vulnerability branch from 6fc374e to c6a6a04 Compare February 17, 2026 23:10
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.

0 participants