agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea 5+ messages / 1 participants [nested] [flat]
* pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea @ 2026-08-10 13:41 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 5+ messages in thread From: Noah Misch @ 2026-08-10 13:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org ecpg: Fix out-of-bound writes due to processing of invalid bytea data ECPG assumes that any bytea data it receives from a backend starts with '\x' as its first two bytes, but a check was missed to enforce that. A rogue server sending some garbage bytea data would be able to crash a client, resulting in a client-side DoS, in the most common cases. Reported-by: ylwangtju <ylwangtju@qq.com> Backpatch-through: 14 Security: CVE-2026-16241 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c7da85fec96666b038fdf83c81dbe1e1573a9e60 Author: Michael Paquier <michael@paquier.xyz> Modified Files -------------- src/interfaces/ecpg/ecpglib/data.c | 7 ++++++ src/interfaces/ecpg/ecpglib/error.c | 7 ++++++ src/interfaces/ecpg/include/ecpgerrno.h | 1 + src/interfaces/ecpg/test/expected/sql-bytea.c | 27 ++++++++++++++++++---- src/interfaces/ecpg/test/expected/sql-bytea.stderr | 24 ++++++++++++++++++- src/interfaces/ecpg/test/sql/bytea.pgc | 5 ++++ 6 files changed, 66 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea @ 2026-08-10 13:41 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 5+ messages in thread From: Noah Misch @ 2026-08-10 13:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org ecpg: Fix out-of-bound writes due to processing of invalid bytea data ECPG assumes that any bytea data it receives from a backend starts with '\x' as its first two bytes, but a check was missed to enforce that. A rogue server sending some garbage bytea data would be able to crash a client, resulting in a client-side DoS, in the most common cases. Reported-by: ylwangtju <ylwangtju@qq.com> Backpatch-through: 14 Security: CVE-2026-16241 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/457b8737ab29ec5e29fc06dcc019795c40e6f261 Author: Michael Paquier <michael@paquier.xyz> Modified Files -------------- src/interfaces/ecpg/ecpglib/data.c | 7 ++++++ src/interfaces/ecpg/ecpglib/error.c | 7 ++++++ src/interfaces/ecpg/include/ecpgerrno.h | 1 + src/interfaces/ecpg/test/expected/sql-bytea.c | 27 ++++++++++++++++++---- src/interfaces/ecpg/test/expected/sql-bytea.stderr | 24 ++++++++++++++++++- src/interfaces/ecpg/test/sql/bytea.pgc | 5 ++++ 6 files changed, 66 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea @ 2026-08-10 13:41 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 5+ messages in thread From: Noah Misch @ 2026-08-10 13:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org ecpg: Fix out-of-bound writes due to processing of invalid bytea data ECPG assumes that any bytea data it receives from a backend starts with '\x' as its first two bytes, but a check was missed to enforce that. A rogue server sending some garbage bytea data would be able to crash a client, resulting in a client-side DoS, in the most common cases. Reported-by: ylwangtju <ylwangtju@qq.com> Backpatch-through: 14 Security: CVE-2026-16241 Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a14ba29b15a8b342808702e9da3e4a4532044f61 Author: Michael Paquier <michael@paquier.xyz> Modified Files -------------- src/interfaces/ecpg/ecpglib/data.c | 7 ++++++ src/interfaces/ecpg/ecpglib/error.c | 7 ++++++ src/interfaces/ecpg/include/ecpgerrno.h | 1 + src/interfaces/ecpg/test/expected/sql-bytea.c | 27 ++++++++++++++++++---- src/interfaces/ecpg/test/expected/sql-bytea.stderr | 24 ++++++++++++++++++- src/interfaces/ecpg/test/sql/bytea.pgc | 5 ++++ 6 files changed, 66 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea @ 2026-08-10 13:41 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 5+ messages in thread From: Noah Misch @ 2026-08-10 13:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org ecpg: Fix out-of-bound writes due to processing of invalid bytea data ECPG assumes that any bytea data it receives from a backend starts with '\x' as its first two bytes, but a check was missed to enforce that. A rogue server sending some garbage bytea data would be able to crash a client, resulting in a client-side DoS, in the most common cases. Reported-by: ylwangtju <ylwangtju@qq.com> Backpatch-through: 14 Security: CVE-2026-16241 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c3c830272a97b9b429eb015c2df206264649c6fc Author: Michael Paquier <michael@paquier.xyz> Modified Files -------------- src/interfaces/ecpg/ecpglib/data.c | 7 ++++++ src/interfaces/ecpg/ecpglib/error.c | 7 ++++++ src/interfaces/ecpg/include/ecpgerrno.h | 1 + src/interfaces/ecpg/test/expected/sql-bytea.c | 27 ++++++++++++++++++---- src/interfaces/ecpg/test/expected/sql-bytea.stderr | 24 ++++++++++++++++++- src/interfaces/ecpg/test/sql/bytea.pgc | 5 ++++ 6 files changed, 66 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea @ 2026-08-10 13:41 Noah Misch <noah@leadboat.com> 0 siblings, 0 replies; 5+ messages in thread From: Noah Misch @ 2026-08-10 13:41 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org ecpg: Fix out-of-bound writes due to processing of invalid bytea data ECPG assumes that any bytea data it receives from a backend starts with '\x' as its first two bytes, but a check was missed to enforce that. A rogue server sending some garbage bytea data would be able to crash a client, resulting in a client-side DoS, in the most common cases. Reported-by: ylwangtju <ylwangtju@qq.com> Backpatch-through: 14 Security: CVE-2026-16241 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/39f855e0e6b461d41680552c40e7f3a3bfd4511f Author: Michael Paquier <michael@paquier.xyz> Modified Files -------------- src/interfaces/ecpg/ecpglib/data.c | 7 ++++++ src/interfaces/ecpg/ecpglib/error.c | 7 ++++++ src/interfaces/ecpg/include/ecpgerrno.h | 1 + src/interfaces/ecpg/test/expected/sql-bytea.c | 27 ++++++++++++++++++---- src/interfaces/ecpg/test/expected/sql-bytea.stderr | 24 ++++++++++++++++++- src/interfaces/ecpg/test/sql/bytea.pgc | 5 ++++ 6 files changed, 66 insertions(+), 5 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-08-10 13:41 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-08-10 13:41 pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea Noah Misch <noah@leadboat.com> 2026-08-10 13:41 pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea Noah Misch <noah@leadboat.com> 2026-08-10 13:41 pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea Noah Misch <noah@leadboat.com> 2026-08-10 13:41 pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea Noah Misch <noah@leadboat.com> 2026-08-10 13:41 pgsql: ecpg: Fix out-of-bound writes due to processing of invalid bytea Noah Misch <noah@leadboat.com>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox