pgproto3 SQL Injection via Protocol Message Size Overflow
Published 4 Mar 2024 · Updated 10 Sept 2026
Is your project on an affected github.com/jackc/pgproto3?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <2.3.3
- Fixed in
- 2.3.3
go get github.com/jackc/pgproto3@v2.3.3- Affected
- <2.3.3
- Fixed in
- 2.3.3
go get github.com/jackc/pgproto3/v2@v2.3.3Details
Impact
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.
Patches
The problem is resolved in v2.3.3
Workarounds
Reject user input large enough to cause a single query or bind message to exceed 4 GB in size.
Is GHSA-7jwh-3vrq-q3m8 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/jackc/pgproto3, and gives you the command that fixes it.
References
- Linkgithub.com/jackc/pgproto3/security/advisories/GHSA-7jwh-3vrq-q3m8
- Linkgithub.com/jackc/pgx/security/advisories/GHSA-mrww-27vc-gghv
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-27304
- Linkgithub.com/jackc/pgproto3/commit/945c2126f6db8f3bea7eeebe307c01fe92bca007
- Linkgithub.com/jackc/pgx/commit/adbb38f298c76e283ffc7c7a3f571036fea47fd4
- Linkgithub.com/jackc/pgx/commit/c543134753a0c5d22881c12404025724cb05ffd8
- Linkgithub.com/jackc/pgx/commit/f94eb0e2f96782042c96801b5ac448f44f0a81df
- Packagegithub.com/jackc/pgproto3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.