Fix possible fix(deps): 6 vulnerable dependencies in go.mod - #130
Open
begininvoke wants to merge 1 commit into
Open
Fix possible fix(deps): 6 vulnerable dependencies in go.mod#130begininvoke wants to merge 1 commit into
begininvoke wants to merge 1 commit into
Conversation
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.
This changes
backend/go.modto address something a scan flagged. It is around line 1.VULNERABILITY: CVE-2024-27304 in github.com/jackc/pgx v3.6.2+incompatible (backend/go.mod). IMPACT: The pgx PostgreSQL driver contains an integer overflow in its protocol message size calculation. If an attacker can influence query parameters such that a single query or bind message exceeds 4 GB in size, the driver incorrectly splits the oversized message into multiple protocol messages with attacker-controlled boundaries. This breaks PostgreSQL wire-protocol framing and allows a potential SQL injection, bypassing parameterized query protections. RISK LEVEL: CRITICAL/HIGH — successful exploitation can lead to arbitrary SQL execution, data exfiltration, or data tampering, especially in applications that accept large user-supplied payloads (blobs, arrays, long text, batch inserts). CURRENT STATE: The project pins v3.6.2+incompatible, which is vulnerable and EOL; there is NO patched v3 release — fixed versions are v4.18.2 and v5.5.4 only. MITIGATION: Upgrading is strongly recommended. The workaround (rejecting user input large enough to exceed 4 GB per message) is fragile and does not remove the root cause.
Updated the vulnerable
github.com/jackc/pgx/v5dependency from v5.7.6 to v5.9.0, addressing the two critical CVEs for this package. The other vulnerabilities either lack a safe upgrade within the same import path or are considered low‑impact (used only in tests/build).For reference: rule
CVE-2024-27304. Rated critical.I may well be missing context here — if the current code is deliberate, feel free to close this.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.