Integer overflow causes an infinite loop in packet buffer growth in PgBouncer
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | PgBouncer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pgbouncer | Pgbouncer |
|
Vendor Workaround
Set max_packet_size well below 1073741824 so that no single packet can grow a packet buffer past the overflow threshold
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.573% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pgbouncer
Pgbouncer pgbouncer |
|
| Vendors & Products |
Pgbouncer
Pgbouncer pgbouncer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Integer overflow in the packet buffer growth logic in PgBouncer through 1.25.2 allows an unauthenticated remote attacker to cause a denial of service. Sufficiently large input makes the buffer size computation overflow, leaving the growth loop unable to terminate. Because PgBouncer serves all clients from a single process, this saturates a CPU core and stalls every pooled connection until the process is killed. Both unauthenticated and authenticated code paths can reach the overflow. | |
| Title | Integer overflow causes an infinite loop in packet buffer growth in PgBouncer | |
| Weaknesses | CWE-190 CWE-835 |
|
| References |
| |
| Metrics |
cvssV3_1
|