diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-11-06 10:29:17 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-11-06 10:29:42 -0500 |
commit | c0c8807ded2f59c25b375998ef24ff09994563a1 (patch) | |
tree | fc8ab6e80444643dd52636201659752213247b38 /doc/bug.template | |
parent | b5002976804cfd42ada725b30cff324ebd3e9638 (diff) |
Make json{b}_populate_recordset() use the right tuple descriptor.
json{b}_populate_recordset() used the tuple descriptor created from the
query-level AS clause without worrying about whether it matched the actual
input record type. If it didn't, that would usually result in a crash,
though disclosure of server memory contents seems possible as well, for a
skilled attacker capable of issuing crafted SQL commands. Instead, use
the query-supplied descriptor only when there is no input tuple to look at,
and otherwise get a tuple descriptor based on the input tuple's own type
marking. The core code will detect any type mismatch in the latter case.
Michael Paquier and Tom Lane, per a report from David Rowley.
Back-patch to 9.3 where this functionality was introduced.
Security: CVE-2017-15098
Diffstat (limited to 'doc/bug.template')
0 files changed, 0 insertions, 0 deletions