pgx is a PostgreSQL driver and toolkit for Go. 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. The problem is resolved in v4.18.2 and v5.5.4. As a workaround, reject user input large enough to cause a single query or bind message to exceed 4 GB in size.
pgx is a PostgreSQL driver and toolkit for Go. 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. The problem is resolved in v4.18.2 and v5.5.4. As a workaround, reject user input large enough to cause a single query or bind message to exceed 4 GB in size.
pgx is a PostgreSQL driver and toolkit for Go. 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. The problem is resolved in v4.18.2 and v5.5.4. As a workaround, reject user input large enough to cause a single query or bind message to exceed 4 GB in size.
### 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.
### 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 v4.18.2 and v5.5.4.
### Workarounds
Reject user input large enough to cause a single query or bind message to exceed 4 GB in size.
An integer overflow in the calculated message size of a query or bind message could allow a single large message to be sent as multiple messages under the attacker's control. This could lead to SQL injection if an attacker can cause a single query or bind message to exceed 4 GB in size.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 6, 2024, 7:07:08 PM
dateUpdated: Dec 12, 2024, 8:52:24 PM
3 related source bulletins · separate from aliases
WID-SEC-W-2024-0626: Red Hat Enterprise Linux: Mehrere Schwachstellen ermöglichen Manipulation von Dateien
CVE-2024-27289 · CVE-2024-27304
msrc_CVE-2024-27304: pgx SQL Injection via Protocol Message Size Overflow
CVE-2024-27304
RHSA-2024:1321: Red Hat Security Advisory: ACS 4.3 enhancement and security update
CVE-2024-27289 · CVE-2024-27304
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-89 · CWE-190
Original publisher date fields
published: 2024-03-06T19:15:08.767
lastModified: 2026-06-17T07:19:36.673
2 source CPE criteria · context only
cpe:2.3:a:jackc:pgproto3:*:*:*:*:*:go:*:*
cpe:2.3:a:jackc:pgx:*:*:*:*:*:go:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.