pgsql: Be more wary about constant's datatype in scalarineqsel(). - Mailing list pgsql-committers

From Noah Misch
Subject pgsql: Be more wary about constant's datatype in scalarineqsel().
Date
Msg-id E1wtQFu-00000000yJ8-2Ern@gemulon.postgresql.org
Whole thread
List pgsql-committers
Be more wary about constant's datatype in scalarineqsel().

The special case here for estimating conditions involving a ctid
column failed to check that the RHS constant is of type tid.
While that'd always be true for the built-in operators that
reference this selectivity estimator, a maliciously constructed
operator could provide a user-controlled Datum value that would
get interpreted as an ItemPointer pointer.  That at least risks
SIGSEGV, and perhaps with a bit of sweat it could be used for
server memory disclosure.

Reported-by: Hcamael <baiyjrh@gmail.com>
Author: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Noah Misch <noah@leadboat.com>
Backpatch-through: 14
Security: CVE-2026-14668

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/005ffaa7fad3a7cc730d94bcf1125b85b8b13ceb
Author: Tom Lane <tgl@sss.pgh.pa.us>

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)


Attachment

pgsql-committers by date:

Previous
From: Noah Misch
Date:
Subject: pgsql: Use value of scram_iterations in mock_scram_secret().
Next
From: Noah Misch
Date:
Subject: pgsql: Obstruct EXTRACT() field name deparse injection.