{"id":"CVE-2021-32029","year":2021,"sequence":32029,"component":"core server","score":6.5,"cvss_version":"3.0","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","first_published":"2021-05-13","source_url":"https://www.postgresql.org/support/security/CVE-2021-32029/","facts":{"affected":{"11":"11","12":"12","13":"13"},"component":"core server","cvss_version":"3.0","description_en":"Using an UPDATE ... RETURNING on a purpose-crafted partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas typically cannot use this attack at will.\n\nThe PostgreSQL project thanks Tom Lane for reporting this problem.","first_published":"2021-05-13","fixed":{"11":"11.12","12":"12.7","13":"13.3"},"id":"CVE-2021-32029","introduced":{},"published":{"11":"2021-05-13","12":"2021-05-13","13":"2021-05-13"},"score":6.5,"title":"Memory disclosure in partitioned-table UPDATE ... RETURNING","url":"https://www.postgresql.org/support/security/CVE-2021-32029/","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"},"reviewed_hash":"6a65a7884245936f6adaef8709d290d460e999dfce1ad78734fa7c9a324ed325","source_hash":"965b9e2323feab543f3cbeb74c418c3a5b43cbefc6594d2862ff0d24dcf8e6a2","text":null,"locales":["en"],"fixes":[{"major":"11","fixed_version":"11.12","introduced":null,"published_date":"2021-05-13","facts":{"fixed":"11.12","introduced":null,"published":"2021-05-13"}},{"major":"12","fixed_version":"12.7","introduced":null,"published_date":"2021-05-13","facts":{"fixed":"12.7","introduced":null,"published":"2021-05-13"}},{"major":"13","fixed_version":"13.3","introduced":null,"published_date":"2021-05-13","facts":{"fixed":"13.3","introduced":null,"published":"2021-05-13"}}],"legacy":[]}