aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-03-17 16:10:37 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-03-17 16:10:37 -0400
commitb77e5d73bcfc0810e7a4eab29cfbc2859adb8db9 (patch)
tree07967caba1cae52a8b757dabf2facf0dceec8a93 /src/backend/executor
parent69739ec317aef5df0ce9258142b3124b6c58b202 (diff)
downloadpostgresql-b77e5d73bcfc0810e7a4eab29cfbc2859adb8db9.tar.gz
postgresql-b77e5d73bcfc0810e7a4eab29cfbc2859adb8db9.zip
Prevent buffer overrun in read_tablespace_map().
Robert Foggia of Trustwave reported that read_tablespace_map() fails to prevent an overrun of its on-stack input buffer. Since the tablespace map file is presumed trustworthy, this does not seem like an interesting security vulnerability, but still we should fix it just in the name of robustness. While here, document that pg_basebackup's --tablespace-mapping option doesn't work with tar-format output, because it doesn't. To make it work, we'd have to modify the tablespace_map file within the tarball sent by the server, which might be possible but I'm not volunteering. (Less-painful solutions would require changing the basebackup protocol so that the source server could adjust the map. That's not very appetizing either.)
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions