Prevent construction of invalid "name" values via element assignment.
Although type "name" is of length NAMEDATALEN, we must not allow the last byte to become nonzero. Otherwise, operations that treat it as a C string will read off the end, resulting in crashes or disclosure of server memory. array_set_element() failed to enforce this. Another bad outcome of element assignment could be to construct an invalidly-encoded multibyte character. Check that too while we're at it. Ideally we'd extend array_set_element()'s API to pass the array type OID, but that's infeasible in released branches, and it seems not worth the trouble even in master given the tiny usage of fixed-length array types. Instead just test for elmlen == 1 && arraytyplen == NAMEDATALEN to decide whether it's a name. Reported-by: Anthropic OSS program Author: Tom Lane <[email protected]> Reviewed-by: Noah Misch <[email protected]> Backpatch-through: 14 Security: CVE-2026-116321 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/5788eaee3f2efd9cd6f01b27dfb49d96d9f2dd0c Author: Tom Lane <[email protected]> Modified Files -------------- src/backend/utils/adt/arrayfuncs.c | 30 +++++++++++++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-)
