pgsql: doc: Expand on proper use of refint.
pgsql: doc: Expand on proper use of refint.
От:
Nathan Bossart <nathan@postgresql.org>
Дата:
doc: Expand on proper use of refint. The security team has received a couple of reports about potential SQL injection via refint's trigger arguments. We discussed this while preparing CVE-2026-6637 and concluded that forcibly quoting these arguments is more likely to break working code than to prevent exploits. Unlike data values, the table/column names come from trigger arguments, and there is little reason for a trigger author to put hostile inputs into those arguments. So, let's document it accordingly. Reported-by: Nikolay Samokhvalov Reported-by: Alex Young Reported-by: Satyanarayana Narlapuram Suggested-by: Noah Misch Reviewed-by: Noah Misch Reviewed-by: Fujii Masao Reviewed-by: Christoph Berg Reviewed-by: Satyanarayana Narlapuram Discussion: https://postgr.es/m/ahXP7z7nsfGPOZ3T%40nathan Backpatch-through: 14 Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/be176e0a6d38bf9007b2192a404f9661a5b5b10a Modified Files -------------- doc/src/sgml/contrib-spi.sgml | 58 ++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 57 insertions(+), 1 deletion(-)