summaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-03-10 14:15:09 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-03-10 14:15:09 -0500
commit0c0a95c2f83b4ed88ebb7f7759c22cd73e7b3cf3 (patch)
treeb49b125d548da2c8835e5d404322c123f04a918d /contrib
parentaf471919bc7e501ee75dd48be763fbdb9c7b530a (diff)
downloadpostgresql-0c0a95c2f83b4ed88ebb7f7759c22cd73e7b3cf3.tar.gz
Sanitize newlines in object names in "pg_restore -l" output.
Commits 89e0bac86 et al replaced newlines with spaces in object names printed in SQL comments, but we neglected to consider that the same names are also printed by "pg_restore -l", and a newline would render the output unparseable by "pg_restore -L". Apply the same replacement in "-l" output. Since "pg_restore -L" doesn't actually examine any object names, only the dump ID field that starts each line, this is enough to fix things for its purposes. The previous fix was treated as a security issue, and we might have done that here as well, except that the issue was reported publicly to start with. Anyway it's hard to see how this could be exploited for SQL injection; "pg_restore -L" doesn't do much with the file except parse it for leading integers. Per bug #14587 from Milos Urbanek. Back-patch to all supported versions. Discussion: https://postgr.es/m/20170310155318.1425.30483@wrigleys.postgresql.org
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions