libguestfs (1:1.44.0-2) unstable; urgency=medium . * Replace bsdmainutils dependency (Closes: #964531, 964533) openvswitch (2.15.0~git20210104.def6eb1ea+dfsg1-5) unstable; urgency=high . * CVE-2020-35498: Packet parsing vulnerability. Applied upstream patch: flow: Support extra padding length.patch (Closes: #982493). postgresql-13 (13.2-1) unstable; urgency=medium . * New upstream version. . + Fix failure to check per-column SELECT privileges in some join queries (Tom Lane) . In some cases involving joins, the parser failed to record all the columns read by a query in the column-usage bitmaps that are used for permissions checking. Although the executor would still insist on some sort of SELECT privilege to run the query, this meant that a user having SELECT privilege on only one column of a table could nonetheless read all its columns through a suitably crafted query. . A stored view that is subject to this problem will have incomplete column-usage bitmaps, and thus permissions will still not be enforced properly on the view after updating. In installations that depend on column-level permissions for security, it is recommended to CREATE OR REPLACE all user-defined views to cause them to be re-parsed. . The PostgreSQL Project thanks Sven Klemm for reporting this problem. (CVE-2021-20229) . + Fix information leakage in constraint-violation error messages (Heikki Linnakangas) . If an UPDATE command attempts to move a row to a different partition but finds that it violates some constraint on the new partition, and the columns in that partition are in different physical positions than in the parent table, the error message could reveal the contents of columns that the user does not have SELECT privilege on. (CVE-2021-3393) . + Fix incorrect detection of concurrent page splits while inserting into a GiST index (Heikki Linnakangas) . Concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. It's recommended to reindex any GiST index that's been subject to concurrent insertions. . + Fix CREATE INDEX CONCURRENTLY to wait for concurrent prepared transactions (Andrey Borodin) . At the point where CREATE INDEX CONCURRENTLY waits for all concurrent transactions to complete so that it can see rows they inserted, it must also wait for all prepared transactions to complete, for the same reason. Its failure to do so meant that rows inserted by prepared transactions might be omitted from the new index, causing queries relying on the index to miss such rows. In installations that have enabled prepared transactions (max_prepared_transactions > 0), it's recommended to reindex any concurrently-built indexes in case this problem occurred when they were built. . [ Christoph Berg ] * Remove obsolete --enable-integer-datetimes configure option. (Closes: #974988) * Modernize server package description. * Use xsltproc --nonet. * run-testsuite: Test only this version. . [ Helmut Grohne ] * Reduce Build-Depends: (Closes: #979456) + gdb is only used for testing. xterm (366-1) unstable; urgency=medium . * New upstream release - correct upper-limit for selection buffer, accounting for combining characters (report/testcase by Tavis Ormandy). Closes: #982439