pgproto3 SQL Injection via Protocol Message Size Overflow

2024-03-0420:45:25

Google

osv.dev

sql injection

protocol message size overflow

integer overflow

patches

workarounds

user input

v2.3.3

software security

9.8 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

7 High

AI Score

Confidence

High

0.0004 Low

EPSS

Percentile

10.3%

JSON

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.

CPENameOperatorVersion
github.com/jackc/pgx/v4lt4.18.2
github.com/jackc/pgproto3/v2lt2.3.3
github.com/jackc/pgproto3lt2.3.3
github.com/jackc/pgx/v5ge5.0.0
github.com/jackc/pgx/v5lt5.5.4

Name	Operator	Version
github.com/jackc/pgx/v4	lt	4.18.2
github.com/jackc/pgproto3/v2	lt	2.3.3
github.com/jackc/pgproto3	lt	2.3.3
github.com/jackc/pgx/v5	ge	5.0.0
github.com/jackc/pgx/v5	lt	5.5.4