build(deps): bump github.com/jackc/pgx/v5 from 5.4.2 to 5.5.4

[dependabot]

Bumps github.com/jackc/pgx/v5 from 5.4.2 to 5.5.4.

Changelog

Sourced from github.com/jackc/pgx/v5's changelog.

5.5.4 (March 4, 2024)

Fix CVE-2024-27304

SQL injection can occur if an attacker can cause a single query or bind message to exceed 4 GB in size. An integer overflow in the calculated message size can cause the one large message to be sent as multiple messages under the attacker's control.

Thanks to Paul Gerste for reporting this issue.

• Fix behavior of CollectRows to return empty slice if Rows are empty (Felix)
• Fix simple protocol encoding of json.RawMessage
• Fix *Pipeline.getResults should close pipeline on error
• Fix panic in TryFindUnderlyingTypeScanPlan (David Kurman)
• Fix deallocation of invalidated cached statements in a transaction
• Handle invalid sslkey file
• Fix scan float4 into sql.Scanner
• Fix pgtype.Bits not making copy of data from read buffer. This would cause the data to be corrupted by future reads.

5.5.3 (February 3, 2024)

• Fix: prepared statement already exists
• Improve CopyFrom auto-conversion of text-ish values
• Add ltree type support (Florent Viel)
• Make some properties of Batch and QueuedQuery public (Pavlo Golub)
• Add AppendRows function (Edoardo Spadolini)
• Optimize convert UUID [16]byte to string (Kirill Malikov)
• Fix: LargeObject Read and Write of more than ~1GB at a time (Mitar)

5.5.2 (January 13, 2024)

• Allow NamedArgs to start with underscore
• pgproto3: Maximum message body length support (jeremy.spriet)
• Upgrade golang.org/x/crypto to v0.17.0
• Add snake_case support to RowToStructByName (Tikhon Fedulov)
• Fix: update description cache after exec prepare (James Hartig)
• Fix: pipeline checks if it is closed (James Hartig and Ryan Fowler)
• Fix: normalize timeout / context errors during TLS startup (Samuel Stauffer)
• Add OnPgError for easier centralized error handling (James Hartig)

5.5.1 (December 9, 2023)

• Add CopyFromFunc helper function. (robford)
• Add PgConn.Deallocate method that uses PostgreSQL protocol Close message.
• pgx uses new PgConn.Deallocate method. This allows deallocating statements to work in a failed transaction. This fixes a case where the prepared statement map could become invalid.
• Fix: Prefer driver.Valuer over json.Marshaler for json fields. (Jacopo)
• Fix: simple protocol SQL sanitizer previously panicked if an invalid $0 placeholder was used. This now returns an error instead. (maksymnevajdev)
• Add pgtype.Numeric.ScanScientific (Eshton Robateau)

5.5.0 (November 4, 2023)

... (truncated)

Commits

• da6f2c9 Update changelog
• c543134 SQL sanitizer wraps arguments in parentheses
• 20344df Check for overflow on uint16 sizes in pgproto3
• adbb38f Do not allow protocol messages larger than ~1GB
• c1b0a01 Fix behavior of CollectRows to return empty slice if Rows are empty
• 88dfc22 Fix simple protocol encoding of json.RawMessage
• 2e84dcc *Pipeline.getResults should close pipeline on error
• d149d3f Fix panic in TryFindUnderlyingTypeScanPlan
• 046f497 deallocateInvalidatedCachedStatements now runs in transactions
• 8896bd6 Handle invalid sslkey file
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Server-Side Request Forgery Analyzer	✅	0 findings
Configured Codepaths Analyzer	✅	0 findings
IDOR Analyzer	✅	0 findings
SQL Injection Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	2 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The code changes in this pull request update the versions of two dependencies used in the project: github.com/jackc/pgx/v5 and github.com/jackc/puddle/v2. These updates are likely to address bug fixes, performance improvements, or new features in the underlying libraries. Keeping dependencies up-to-date is a good security practice, as it helps mitigate potential vulnerabilities in the codebase.

However, it's important to thoroughly test the application after updating dependencies to ensure that the changes do not introduce any regressions or unexpected behavior. Additionally, it's a good idea to review the release notes and changelogs for the updated dependencies to understand the nature of the changes and any potential security implications.

Overall, this code change appears to be a routine dependency update, which is a common practice in software development. As long as the updates are properly tested and validated, they should not raise any major security concerns.

Files Changed:

1. go.mod: This file has been updated to use newer versions of the github.com/jackc/pgx/v5 (from v5.4.2 to v5.5.4) and github.com/jackc/puddle/v2 (from v2.2.0 to v2.2.1) dependencies.

2. go.sum: This file has been updated to reflect the changes in the dependency versions, as described in the go.mod file.

Powered by DryRun Security

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity	Details
High	pkg:golang/github.com/jackc/pgx/v5@v5.5.4 upgrade to: > v5.5.4

More info on how to fix Vulnerable Libraries in Go.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.