diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-11-06 10:29:16 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-11-06 10:29:39 -0500 |
commit | 38e825632be777a6ea4a39796e121c39728403b3 (patch) | |
tree | 4206ec6d92cd7d61f75e81de9806c730ee308bca /src/backend/regex | |
parent | b7d6f75072b3569d7d2acce04669e72086b547cb (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 'src/backend/regex')
0 files changed, 0 insertions, 0 deletions