{"id":"CVE-2024-10977","aliases":["ALPINE-CVE-2024-10977","AZL-53195","AZL-53206","BELL-CVE-2024-10977","BIT-postgresql-2024-10977","CLSA-2025-1747431041","CLSA-2026-1779707025","DEBIAN-CVE-2024-10977","DLA-3954-1","DSA-5812-1","EUVD-2024-33375","GHSA-62q4-hc79-94qj","JLSEC-2026-48","MGASA-2024-0372","OESA-2024-2427","OESA-2024-2428","OESA-2024-2429","OESA-2024-2430","OESA-2024-2466","OESA-2024-2467","OESA-2024-2468","OESA-2024-2469","OESA-2025-1335","SUSE-SU-2024:4052-1","SUSE-SU-2024:4063-1","SUSE-SU-2024:4095-1","SUSE-SU-2024:4096-1","SUSE-SU-2024:4097-1","SUSE-SU-2024:4098-1","SUSE-SU-2024:4099-1","SUSE-SU-2024:4114-1","SUSE-SU-2024:4118-1","SUSE-SU-2024:4173-1","SUSE-SU-2024:4174-1","SUSE-SU-2024:4175-1","SUSE-SU-2024:4176-1","SUSE-SU-2025:01799-1","UBUNTU-CVE-2024-10977","USN-7132-1","USN-7358-1","openSUSE-SU-2024:14501-1","openSUSE-SU-2024:14502-1","openSUSE-SU-2024:14503-1","openSUSE-SU-2024:14504-1","openSUSE-SU-2024:14505-1","openSUSE-SU-2024:14506-1"],"status":"published","title":"PostgreSQL libpq retains an error message from man-in-the-middle","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","severity":{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00398,"percentile":0.34365,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-345","CWE-348"],"published":"2024-11-14T13:00:05Z","modified":"2026-11-03T06:32:03Z","fixes":[{"ecosystem":"Alpine:v3.17","package":"postgresql13","fixed_in":["13.17-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"postgresql13","fixed_in":["13.17-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"postgresql13","fixed_in":["13.17-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"postgresql14","fixed_in":["14.14-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"postgresql14","fixed_in":["14.14-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"postgresql14","fixed_in":["14.14-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"postgresql14","fixed_in":["14.14-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"postgresql16","fixed_in":["16.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"postgresql17","fixed_in":["17.1-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql17","fixed_in":["17.1-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"postgresql17","fixed_in":["17.1-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"postgresql17","fixed_in":["17.1-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"postgresql","fixed_in":["14.14-1"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"postgresql","fixed_in":["16.5-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"postgresql15","fixed_in":["15.9-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"postgresql17","fixed_in":["17.1-r0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"postgresql","fixed_in":["12.21.0","13.17.0","14.14.0","15.9.0","16.5.0","17.1.0"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-contrib","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-docs","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-plperl","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-plpython3","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-pltcl","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-private-devel","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-private-libs","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-server","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-server-devel","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-static","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-test","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-test-rpm-macros","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-upgrade","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-upgrade-devel","fixed_in":["13.11-1.el9_2.tuxcare.els18"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"postgresql-15","fixed_in":["15.9-0+deb12u1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"postgresql-17","fixed_in":["17.1-1"],"sources":["osv"]},{"ecosystem":"Julia","package":"LibPQ_jll","fixed_in":["16.8.0+0"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"postgresql-9.5","fixed_in":["9.5.25-0ubuntu0.16.04.1+esm10"],"sources":["osv"]},{"ecosystem":"Ubuntu:20.04:LTS","package":"postgresql-12","fixed_in":["12.22-0ubuntu0.20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","fixed_in":["14.15-0ubuntu0.22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","fixed_in":["16.6-0ubuntu0.24.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.17","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-r0"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-1"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"15.2-r0"},{"fixed":"15.9-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.0-r1"},{"fixed":"17.1-r0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"postgresql","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"12.21.0"},{"introduced":"13.0.0"},{"fixed":"13.17.0"},{"introduced":"14.0.0"},{"fixed":"14.14.0"},{"introduced":"15.0.0"},{"fixed":"15.9.0"},{"introduced":"16.0.0"},{"fixed":"16.5.0"},{"introduced":"17.0.0"},{"fixed":"17.1.0"}]}]},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libecpg-compat3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libecpg-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libecpg6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libpgtypes3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libpq-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"libpq5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-client-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-contrib-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-doc-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-plperl-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-plpython-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-plpython3-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-pltcl-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"postgresql-server-dev-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+tuxcare.els10"}]}],"bundled":2},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-contrib","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-plperl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-plpython3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-pltcl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-private-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-private-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-server-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-test","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-test-rpm-macros","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-upgrade","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"postgresql-upgrade-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.11-1.el9_2.tuxcare.els18"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"postgresql-15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-0+deb12u1"}]}],"versions":["15.3-0+deb12u1","15.3-1","15.4-0+deb12u1","15.4-1","15.4-2","15.4-3","15.5-0+deb12u1","15.6-0+deb12u1","15.7-0+deb12u1","15.8-0+deb12u1"]},{"source":"osv","ecosystem":"Debian:13","package":"postgresql-17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-1"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"postgresql-13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-0+deb11u1"}]}],"versions":["13.10-0+deb11u1","13.11-0+deb11u1","13.12-0+deb11u1","13.13-0+deb11u1","13.14-0+deb11u1","13.15-0+deb11u1","13.16-0+deb11u1","13.3-1","13.4-0+deb11u1","13.4-1","13.4-2","13.4-3","13.5-0+deb11u1","13.7-0+deb11u1","13.8-0+deb11u1","13.9-0+deb11u1"],"bundled":4},{"source":"osv","ecosystem":"Debian:12","package":"postgresql-15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-0+deb12u1"}]}],"versions":["15.3-0+deb12u1","15.3-1","15.4-0+deb12u1","15.4-1","15.4-2","15.4-3","15.5-0+deb12u1","15.6-0+deb12u1","15.7-0+deb12u1","15.8-0+deb12u1"],"bundled":4},{"source":"osv","ecosystem":"Julia","package":"LibPQ_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"16.8.0+0"}]}]},{"source":"osv","ecosystem":"Mageia:9","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-1.mga9"}]}],"bundled":4},{"source":"osv","ecosystem":"Mageia:9","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-1.mga9"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"libpq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp3"}]}],"bundled":5},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"libpq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp1"}]}],"bundled":8},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"libpq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-1.oe2403"}]}],"bundled":5},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"libpq","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp4"}]}],"bundled":5},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-1.oe2403"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp4"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp3"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP1","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.oe2203sp1"}]}],"bundled":4},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"postgresql-13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.20-1.oe2003sp4"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150600.17.6.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150600.16.10.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150600.13.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150600.17.6.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150600.16.10.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150600.13.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150600.17.6.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150600.16.10.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP6","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150600.13.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150600.17.6.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150600.16.10.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150600.13.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-3.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-3.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-3.49.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-3.49.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-3.63.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-3.63.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150600.16.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150600.16.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-150200.8.66.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-3.55.2"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-3.55.2"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP6","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150600.16.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP6","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150600.16.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150600.16.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150500.10.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150500.10.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150500.10.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150500.10.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150200.4.30.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150300.10.27.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150200.4.30.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150300.10.27.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150200.4.30.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150300.10.27.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150400.4.18.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150300.10.27.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-150500.10.9.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-150200.5.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-150200.5.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.10-150200.5.33.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.18-150200.5.64.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Proxy 4.3","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Manager Server 4.3","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-150200.5.50.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-4.29.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-3.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-3.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17-4.29.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-3.21.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.2-3.5.1"}]}],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"postgresql-9.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["9.3.1-1","9.3.2-1","9.3.2-1ubuntu1","9.3.2-1ubuntu2","9.3.3-1","9.3.3-1bzr1","9.3.3-1bzr2","9.3.4-1","9.3.5-0ubuntu0.14.04.1","9.3.6-0ubuntu0.14.04","9.3.7-0ubuntu0.14.04","9.3.8-0ubuntu0.4.04","9.3.9-0ubuntu0.14.04","9.3.10-0ubuntu0.14.04","9.3.11-0ubuntu0.14.04","9.3.12-0ubuntu0.14.04","9.3.13-0ubuntu0.14.04","9.3.14-0ubuntu0.14.04","9.3.15-0ubuntu0.14.04","9.3.16-0ubuntu0.14.04","9.3.17-0ubuntu0.14.04","9.3.18-0ubuntu0.14.04.1","9.3.19-0ubuntu0.14.04","9.3.20-0ubuntu0.14.04","9.3.21-0ubuntu0.14.04","9.3.22-0ubuntu0.14.04","9.3.23-0ubuntu0.14.04","9.3.24-0ubuntu0.14.04","9.3.24-0ubuntu0.14.04+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"postgresql-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+esm10"}]}],"versions":["9.5.0-1","9.5.0-2","9.5.0-3","9.5.1-1","9.5.2-1","9.5.3-0ubuntu0.16.04","9.5.4-0ubuntu0.16.04","9.5.5-0ubuntu0.16.04","9.5.6-0ubuntu0.16.04","9.5.7-0ubuntu0.16.04","9.5.8-0ubuntu0.16.04.1","9.5.9-0ubuntu0.16.04","9.5.10-0ubuntu0.16.04","9.5.11-0ubuntu0.16.04","9.5.12-0ubuntu0.16.04","9.5.13-0ubuntu0.16.04","9.5.14-0ubuntu0.16.04","9.5.16-0ubuntu0.16.04.1","9.5.17-0ubuntu0.16.04.1","9.5.18-0ubuntu0.16.04.1","9.5.19-0ubuntu0.16.04.1","9.5.21-0ubuntu0.16.04.1","9.5.23-0ubuntu0.16.04.1","9.5.24-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1+esm1","9.5.25-0ubuntu0.16.04.1+esm2","9.5.25-0ubuntu0.16.04.1+esm3","9.5.25-0ubuntu0.16.04.1+esm4","9.5.25-0ubuntu0.16.04.1+esm5","9.5.25-0ubuntu0.16.04.1+esm6","9.5.25-0ubuntu0.16.04.1+esm7","9.5.25-0ubuntu0.16.04.1+esm8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"postgresql-10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.1-1","10.1-2","10.2-1","10.3-1","10.4-0ubuntu0.18.04","10.5-0ubuntu0.18.04","10.6-0ubuntu0.18.04.1","10.7-0ubuntu0.18.04.1","10.8-0ubuntu0.18.04.1","10.9-0ubuntu0.18.04.1","10.10-0ubuntu0.18.04.1","10.12-0ubuntu0.18.04.1","10.14-0ubuntu0.18.04.1","10.15-0ubuntu0.18.04.1","10.16-0ubuntu0.18.04.1","10.17-0ubuntu0.18.04.1","10.18-0ubuntu0.18.04.1","10.19-0ubuntu0.18.04.1","10.20-0ubuntu0.18.04.1","10.21-0ubuntu0.18.04.1","10.22-0ubuntu0.18.04.1","10.23-0ubuntu0.18.04.1","10.23-0ubuntu0.18.04.2","10.23-0ubuntu0.18.04.2+esm1","10.23-0ubuntu0.18.04.2+esm2","10.23-0ubuntu0.18.04.2+esm3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"postgresql-12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-0ubuntu0.20.04.1"}]}],"versions":["12.0-1","12.1-1","12.1-2build1","12.2-1","12.2-1ubuntu2","12.2-4","12.4-0ubuntu0.20.04.1","12.5-0ubuntu0.20.04.1","12.6-0ubuntu0.20.04.1","12.7-0ubuntu0.20.04.1","12.8-0ubuntu0.20.04.1","12.9-0ubuntu0.20.04.1","12.10-0ubuntu0.20.04.1","12.11-0ubuntu0.20.04.1","12.12-0ubuntu0.20.04.1","12.13-0ubuntu0.20.04.1","12.14-0ubuntu0.20.04.1","12.15-0ubuntu0.20.04.1","12.16-0ubuntu0.20.04.1","12.17-0ubuntu0.20.04.1","12.18-0ubuntu0.20.04.1","12.19-0ubuntu0.20.04.1","12.20-0ubuntu0.20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-0ubuntu0.22.04.1"}]}],"versions":["14.1-1ubuntu1","14.2-1","14.2-1ubuntu1","14.3-0ubuntu0.22.04.1","14.4-0ubuntu0.22.04.1","14.5-0ubuntu0.22.04.1","14.6-0ubuntu0.22.04.1","14.7-0ubuntu0.22.04.1","14.8-0ubuntu0.22.04.1","14.9-0ubuntu0.22.04.1","14.10-0ubuntu0.22.04.1","14.11-0ubuntu0.22.04.1","14.12-0ubuntu0.22.04.1","14.13-0ubuntu0.22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-0ubuntu0.24.04.1"}]}],"versions":["16.0-2","16.1-1","16.1-1build1","16.1-1build3","16.2-1","16.2-1ubuntu2","16.2-1ubuntu3","16.2-1ubuntu4","16.3-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"postgresql-12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22-0ubuntu0.20.04.1"}]}],"versions":["12.0-1","12.1-1","12.1-2build1","12.2-1","12.2-1ubuntu2","12.2-4","12.4-0ubuntu0.20.04.1","12.5-0ubuntu0.20.04.1","12.6-0ubuntu0.20.04.1","12.7-0ubuntu0.20.04.1","12.8-0ubuntu0.20.04.1","12.9-0ubuntu0.20.04.1","12.10-0ubuntu0.20.04.1","12.11-0ubuntu0.20.04.1","12.12-0ubuntu0.20.04.1","12.13-0ubuntu0.20.04.1","12.14-0ubuntu0.20.04.1","12.15-0ubuntu0.20.04.1","12.16-0ubuntu0.20.04.1","12.17-0ubuntu0.20.04.1","12.18-0ubuntu0.20.04.1","12.19-0ubuntu0.20.04.1","12.20-0ubuntu0.20.04.1"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.15-0ubuntu0.22.04.1"}]}],"versions":["14.1-1ubuntu1","14.2-1","14.2-1ubuntu1","14.3-0ubuntu0.22.04.1","14.4-0ubuntu0.22.04.1","14.5-0ubuntu0.22.04.1","14.6-0ubuntu0.22.04.1","14.7-0ubuntu0.22.04.1","14.8-0ubuntu0.22.04.1","14.9-0ubuntu0.22.04.1","14.10-0ubuntu0.22.04.1","14.11-0ubuntu0.22.04.1","14.12-0ubuntu0.22.04.1","14.13-0ubuntu0.22.04.1"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.6-0ubuntu0.24.04.1"}]}],"versions":["16.0-2","16.1-1","16.1-1build1","16.1-1build3","16.2-1","16.2-1ubuntu2","16.2-1ubuntu3","16.2-1ubuntu4","16.3-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.2"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"postgresql-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.5.25-0ubuntu0.16.04.1+esm10"}]}],"versions":["9.5.0-1","9.5.0-2","9.5.0-3","9.5.1-1","9.5.2-1","9.5.3-0ubuntu0.16.04","9.5.4-0ubuntu0.16.04","9.5.5-0ubuntu0.16.04","9.5.6-0ubuntu0.16.04","9.5.7-0ubuntu0.16.04","9.5.8-0ubuntu0.16.04.1","9.5.9-0ubuntu0.16.04","9.5.10-0ubuntu0.16.04","9.5.11-0ubuntu0.16.04","9.5.12-0ubuntu0.16.04","9.5.13-0ubuntu0.16.04","9.5.14-0ubuntu0.16.04","9.5.16-0ubuntu0.16.04.1","9.5.17-0ubuntu0.16.04.1","9.5.18-0ubuntu0.16.04.1","9.5.19-0ubuntu0.16.04.1","9.5.21-0ubuntu0.16.04.1","9.5.23-0ubuntu0.16.04.1","9.5.24-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1+esm1","9.5.25-0ubuntu0.16.04.1+esm2","9.5.25-0ubuntu0.16.04.1+esm3","9.5.25-0ubuntu0.16.04.1+esm4","9.5.25-0ubuntu0.16.04.1+esm5","9.5.25-0ubuntu0.16.04.1+esm6","9.5.25-0ubuntu0.16.04.1+esm7","9.5.25-0ubuntu0.16.04.1+esm8"],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.21-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.17-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.14-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.9-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.5-1.1"}]}],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.1-1.1"}]}],"bundled":4}],"products":[{"vendor":"postgresql","product":"postgresql"}],"references":[{"url":"https://www.postgresql.org/support/security/CVE-2024-10977/","tags":["Vendor Advisory","advisory","web","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2024/11/msg00011.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-10977","tags":["web","advisory"]},{"url":"https://www.postgresql.org/support/security/CVE-2024-10977"},{"url":"https://github.com/advisories/GHSA-62q4-hc79-94qj"},{"url":"https://security.alpinelinux.org/vuln/CVE-2024-10977","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2024-10977","tags":["advisory"]},{"url":"https://errata.cloudlinux.com/ubuntu16-els/CLSA-2025-1747431041.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1779707025.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6474","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6637","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2024-10977","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2024-0372.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=33779","tags":["report"]},{"url":"https://www.postgresql.org/about/news/postgresql-171-165-159-1414-1317-and-1221-released-2955/","tags":["web"]},{"url":"https://www.postgresql.org/about/news/postgresql-172-166-1510-1415-1318-and-1222-released-2965/","tags":["web"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-0985","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-10976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-10978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-10979","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-5868","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-5869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-5870","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2429","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2430","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2466","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2467","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2468","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2469","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1335","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-3677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-39417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-7348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-1094","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244052-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1219340","tags":["report"]},{"url":"https://bugzilla.suse.com/1230423","tags":["report"]},{"url":"https://bugzilla.suse.com/1233323","tags":["report"]},{"url":"https://bugzilla.suse.com/1233325","tags":["report"]},{"url":"https://bugzilla.suse.com/1233326","tags":["report"]},{"url":"https://bugzilla.suse.com/1233327","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-10976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-10977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-10978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-10979","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244063-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244095-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244096-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244097-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244098-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244099-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244114-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244118-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244173-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244174-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244175-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20244176-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2025/suse-su-202501799-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-10977","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-10977","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-7132-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-7358-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-10976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-10978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-10979","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/AKWDFN2C7BDHNEIL7UAMUE2QLH322LIK/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/RB4KENPNXIDYL7D4OSLN7SICCC2ASXXP/","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2024-10977","title":"PostgreSQL libpq retains an error message from man-in-the-middle","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:00:05.715Z","modified":"2025-11-03T21:51:38.414Z","cvss":[{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low","assessor":"cna"}],"cwes":["CWE-348"],"updated_at":"2026-11-02T14:34:02.321514Z"}],"euvd":[{"id":"EUVD-2024-33375","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:00:05Z","modified":"2025-11-03T21:51:38Z","cvss":[{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T19:49:30.775561Z"}],"ghsa":[{"id":"GHSA-62q4-hc79-94qj","title":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or...","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T15:32:15Z","modified":"2025-11-04T00:32:04Z","cvss":[{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low"}],"cwes":["CWE-345","CWE-348"],"updated_at":"2026-11-02T15:04:30.147215Z"}],"nvd":[{"id":"CVE-2024-10977","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04.023Z","modified":"2026-06-17T06:56:49.087Z","cvss":[{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low","assessor":"secondary"},{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low","assessor":"primary"}],"cwes":["CWE-348","CWE-345"],"updated_at":"2026-11-02T14:10:37.281254Z"}],"osv":[{"id":"ALPINE-CVE-2024-10977","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04.023Z","modified":"2026-11-03T06:32:03.827095235Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-03T07:18:15.355745Z"},{"id":"AZL-53195","title":"CVE-2024-10977 affecting package postgresql for versions less than 14.14-1","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04Z","modified":"2026-04-21T04:33:37.95526Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:28:06.595149Z"},{"id":"AZL-53206","title":"CVE-2024-10977 affecting package postgresql for versions less than 16.5-1","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04Z","modified":"2026-04-21T04:56:24.949377Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:28:06.595149Z"},{"id":"BELL-CVE-2024-10977","status":"published","published":"2024-11-16T05:58:55.868708Z","modified":"2026-01-26T09:42:47.931947Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:28:19.288949Z"},{"id":"CVE-2024-10977","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04.023Z","modified":"2026-04-16T04:35:09.787846596Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:44:37.180532Z"},{"id":"DEBIAN-CVE-2024-10977","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:04.023Z","modified":"2026-11-02T12:00:36.816740347Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:45:41.849198Z"},{"id":"JLSEC-2026-48","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2026-04-03T13:27:15.647Z","modified":"2026-07-18T00:02:07.179626191Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T15:47:18.573531Z"},{"id":"OESA-2024-2427","title":"libpq security update","description":"PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. This package provides the essential shared library for any PostgreSQL client program or interface.\r\n\r\nSecurity Fix(es):\r\n\r\nLate privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker\u0026apos;s roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker\u0026apos;s materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.(CVE-2024-0985)\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:54Z","modified":"2026-08-18T01:18:39.498649777Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2428","title":"libpq security update","description":"PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. This package provides the essential shared library for any PostgreSQL client program or interface.\r\n\r\nSecurity Fix(es):\r\n\r\nA memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with \u0026apos;unknown\u0026apos;-type arguments. Handling \u0026apos;unknown\u0026apos;-type values from string literals without type designation can disclose bytes, potentially revealing notable and confidential information. This issue exists due to excessive data output in aggregate function calls, enabling remote users to read some portion of system memory.(CVE-2023-5868)\r\n\r\nA flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overflow by providing specially crafted data. This enables the execution of arbitrary code on the target system, allowing users to write arbitrary bytes to memory and extensively read the server\u0026apos;s memory.(CVE-2023-5869)\r\n\r\nA flaw was found in PostgreSQL involving the pg_cancel_backend role that signals background workers, including the logical replication launcher, autovacuum workers, and the autovacuum launcher. Successful exploitation requires a non-core extension with a less-resilient background worker and would affect that specific background worker only. This issue may allow a remote high privileged user to launch a denial of service (DoS) attack.(CVE-2023-5870)\r\n\r\nLate privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker\u0026apos;s roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker\u0026apos;s materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.(CVE-2024-0985)\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:54Z","modified":"2026-08-18T01:18:38.932898261Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2429","title":"libpq security update","description":"PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. This package provides the essential shared library for any PostgreSQL client program or interface.\r\n\r\nSecurity Fix(es):\r\n\r\nLate privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker\u0026apos;s roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker\u0026apos;s materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.(CVE-2024-0985)\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:54Z","modified":"2026-08-18T01:18:39.266390272Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2430","title":"libpq security update","description":"PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. This package provides the essential shared library for any PostgreSQL client program or interface.\r\n\r\nSecurity Fix(es):\r\n\r\nLate privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker\u0026apos;s roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker\u0026apos;s materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.(CVE-2024-0985)\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:54Z","modified":"2026-08-18T01:18:38.898625782Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2466","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):PostgreSQL is an advanced Object-Relational database management system (DBMS).\nThe base postgresql package contains the client programs that you\u0026apos;ll need to\naccess a PostgreSQL DBMS server, as well as HTML documentation for the whole\nsystem.  These client programs can be located on the same machine as the\nPostgreSQL server, or on a remote machine that accesses a PostgreSQL server\nover a network connection.  The PostgreSQL server can be found in the\npostgresql-server sub-package.\r\n\r\nSecurity Fix(es):\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:56Z","modified":"2026-08-18T01:18:40.311658316Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2467","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):PostgreSQL is an advanced Object-Relational database management system (DBMS).\nThe base postgresql package contains the client programs that you\u0026apos;ll need to\naccess a PostgreSQL DBMS server, as well as HTML documentation for the whole\nsystem.  These client programs can be located on the same machine as the\nPostgreSQL server, or on a remote machine that accesses a PostgreSQL server\nover a network connection.  The PostgreSQL server can be found in the\npostgresql-server sub-package.\r\n\r\nSecurity Fix(es):\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:56Z","modified":"2026-08-18T01:18:41.640790529Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2468","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):PostgreSQL is an advanced Object-Relational database management system (DBMS).\nThe base postgresql package contains the client programs that you\u0026apos;ll need to\naccess a PostgreSQL DBMS server, as well as HTML documentation for the whole\nsystem.  These client programs can be located on the same machine as the\nPostgreSQL server, or on a remote machine that accesses a PostgreSQL server\nover a network connection.  The PostgreSQL server can be found in the\npostgresql-server sub-package.\r\n\r\nSecurity Fix(es):\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:56Z","modified":"2026-08-18T01:18:41.610211895Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2024-2469","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):PostgreSQL is an advanced Object-Relational database management system (DBMS).\nThe base postgresql package contains the client programs that you\u0026apos;ll need to\naccess a PostgreSQL DBMS server, as well as HTML documentation for the whole\nsystem.  These client programs can be located on the same machine as the\nPostgreSQL server, or on a remote machine that accesses a PostgreSQL server\nover a network connection.  The PostgreSQL server can be found in the\npostgresql-server sub-package.\r\n\r\nSecurity Fix(es):\r\n\r\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\r\n\r\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\r\n\r\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\r\n\r\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)","status":"published","published":"2024-11-22T11:07:57Z","modified":"2026-08-18T01:18:41.618109776Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.253598Z"},{"id":"OESA-2025-1335","title":"postgresql-13 security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026amp;apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):\n\nA flaw was found in postgresql. A purpose-crafted query can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can complete this attack at will. The attack does not require the ability to create objects. If server settings include max_worker_processes=0, the known versions of this attack are infeasible. However, undiscovered variants of the attack may be independent of that setting.(CVE-2021-3677)\n\nIN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, \u0026apos;\u0026apos;, or \u0026quot;\u0026quot;). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, an attacker with database-level CREATE privilege can execute arbitrary code as the bootstrap superuser.(CVE-2023-39417)\n\nA memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with \u0026apos;unknown\u0026apos;-type arguments. Handling \u0026apos;unknown\u0026apos;-type values from string literals without type designation can disclose bytes, potentially revealing notable and confidential information. This issue exists due to excessive data output in aggregate function calls, enabling remote users to read some portion of system memory.(CVE-2023-5868)\n\nA flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overflow by providing specially crafted data. This enables the execution of arbitrary code on the target system, allowing users to write arbitrary bytes to memory and extensively read the server\u0026apos;s memory.(CVE-2023-5869)\n\nA flaw was found in PostgreSQL involving the pg_cancel_backend role that signals background workers, including the logical replication launcher, autovacuum workers, and the autovacuum launcher. Successful exploitation requires a non-core extension with a less-resilient background worker and would affect that specific background worker only. This issue may allow a remote high privileged user to launch a denial of service (DoS) attack.(CVE-2023-5870)\n\nLate privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker\u0026apos;s roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker\u0026apos;s materialized view. Versions before PostgreSQL 16.2, 15.6, 14.11, 13.14, and 12.18 are affected.(CVE-2024-0985)\n\nIncomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles.  This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a particular application\u0026apos;s pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10976)\n\nClient use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10977)\n\nIncorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker.  If that query reacts to current_setting(\u0026apos;role\u0026apos;) or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10978)\n\nIncorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.(CVE-2024-10979)\n\nTime-of-check Time-of-use (TOCTOU) race condition in pg_dump in PostgreSQL allows an object creator to execute arbitrary SQL functions as the user running pg_dump, which is often a superuser. The attack involves replacing another relation type with a view or foreign table. The attack requires waiting for pg_dump to start, but winning the race condition is trivial if the attacker retains an open transaction. Versions before PostgreSQL 16.4, 15.8, 14.13, 13.16, and 12.20 are affected.(CVE-2024-7348)\n\nImproper neutralization of quoting syntax in PostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() allows a database input provider to achieve SQL injection in certain usage patterns.  Specifically, SQL injection requires the application to use the function result to construct input to psql, the PostgreSQL interactive terminal.  Similarly, improper neutralization of quoting syntax in PostgreSQL command line utility programs allows a source of command line arguments to achieve SQL injection when client_encoding is BIG5 and server_encoding is one of EUC_TW or MULE_INTERNAL.  Versions before PostgreSQL 17.3, 16.7, 15.11, 14.16, and 13.19 are affected.(CVE-2025-1094)","status":"published","published":"2025-03-29T11:08:26Z","modified":"2026-08-18T01:17:50.355316753Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"UBUNTU-CVE-2024-10977","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-14T13:15:00Z","modified":"2026-04-22T14:37:09.389328Z","cvss":[{"version":"3.1","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"low"},{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-02T16:54:41.555387Z"},{"id":"BIT-postgresql-2024-10977","title":"PostgreSQL libpq retains an error message from man-in-the-middle","description":"Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application.  For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results.  This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.","status":"published","published":"2024-11-16T07:16:52.278Z","modified":"2026-09-10T16:01:45.94279052Z","updated_at":"2026-11-02T15:28:34.724063Z"},{"id":"CLSA-2025-1747431041","title":"Fix CVE(s): CVE-2024-10976, CVE-2024-10977","description":"   * SECURITY UPDATE: incomplete tracking of row security allows unauthorized\n     access to data\n     - debian/patches/CVE-2024-10976.patch: Ensure cached plans to be correctly\n       marked as dependent on role to fix the issue of neglected marking which\n       could lead to incorrect row visibility.\n     - CVE-2024-10976\n   * SECURITY UPDATE: server error message leakage\n     - debian/patches/CVE-2024-10977.patch: Discard error messages received\n       during SSL and GSS negotiation to prevent arbitrary bytes written to the\n       client's terminal\n     - CVE-2024-10977","status":"published","published":"2025-05-16T21:30:46Z","modified":"2026-06-04T10:03:27.099838Z","updated_at":"2026-11-02T15:43:41.66212Z"},{"id":"CLSA-2026-1779707025","title":"postgresql: Fix of 8 CVEs","description":"- CVE-2024-10977: libpq retains untrusted error message bytes from a\n  man-in-the-middle during SSL/GSS negotiation; bail out and discard the\n  server-provided text so the client does not write arbitrary non-NUL bytes\n  to a terminal","status":"published","published":"2026-06-10T14:38:19Z","modified":"2026-10-26T09:30:04.616039068Z","updated_at":"2026-11-02T15:43:45.090939Z"},{"id":"DLA-3954-1","title":"postgresql-13 - security update","status":"published","published":"2024-11-16T00:00:00Z","modified":"2026-03-09T01:18:42.602627Z","updated_at":"2026-11-02T15:46:12.203458Z"},{"id":"DSA-5812-1","title":"postgresql-15 - security update","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-03-09T02:10:47.506286Z","updated_at":"2026-11-02T15:46:17.892347Z"},{"id":"MGASA-2024-0372","title":"Updated postgresql15 \u0026 postgresql13 packages fix security vulnerabilities","description":"PostgreSQL row security below e.g. subqueries disregards user ID\nchanges. (CVE-2024-10976)\nPostgreSQL libpq retains an error message from man-in-the-middle.\n(CVE-2024-10977)\nPostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID.\n(CVE-2024-10978)\nPostgreSQL PL/Perl environment variable changes execute arbitrary code.\n(CVE-2024-10979)\n","status":"published","published":"2024-11-27T19:59:10Z","modified":"2026-04-16T04:42:04.992945001Z","updated_at":"2026-11-02T15:49:42.684501Z"},{"id":"openSUSE-SU-2024:14501-1","title":"postgresql12-12.21-1.1 on GA media","description":"These are all security issues fixed in the postgresql12-12.21-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T03:22:27.576482Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2024:14502-1","title":"postgresql13-13.17-1.1 on GA media","description":"These are all security issues fixed in the postgresql13-13.17-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2025-05-07T18:15:40.29711Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2024:14503-1","title":"postgresql14-14.14-1.1 on GA media","description":"These are all security issues fixed in the postgresql14-14.14-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T03:42:23.434188Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2024:14504-1","title":"postgresql15-15.9-1.1 on GA media","description":"These are all security issues fixed in the postgresql15-15.9-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T03:59:42.304525Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2024:14505-1","title":"postgresql16-16.5-1.1 on GA media","description":"These are all security issues fixed in the postgresql16-16.5-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T04:33:53.803185Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"openSUSE-SU-2024:14506-1","title":"libecpg6-17.1-1.1 on GA media","description":"These are all security issues fixed in the libecpg6-17.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-11-15T00:00:00Z","modified":"2026-02-04T03:30:33.311078Z","updated_at":"2026-11-02T16:58:36.976155Z"},{"id":"SUSE-SU-2024:4052-1","title":"Security update for postgresql, postgresql16, postgresql17","description":"This update for postgresql, postgresql16, postgresql17 fixes the following issues:\n\nThis update ships postgresql17 , and fixes security issues with postgresql16:\n\n- bsc#1230423: Relax the dependency of extensions on the server\n  version from exact major.minor to greater or equal, after Tom\n  Lane confirmed on the PostgreSQL packagers list that ABI\n  stability is being taken care of between minor releases.\n\n- bsc#1219340: The last fix was not correct. Improve it by removing\n  the dependency again and call fillup only if it is installed.\n\npostgresql16 was updated to 16.6:\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n* https://www.postgresql.org/docs/release/16.6/\n\npostgresql16 was updated to 16.5:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/16.5/\n\n- Don't build the libs and mini flavor anymore to hand over to\n  PostgreSQL 17.\n\n  * https://www.postgresql.org/about/news/p-2910/\n\npostgresql17 is shipped in version 17.2:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/17.1/\n* https://www.postgresql.org/docs/release/17.2/\n\nUpgrade to 17.2:\n\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n\nUpgrade to 17.0:\n\n* New memory management system for VACUUM, which reduces memory\n  consumption and can improve overall vacuuming performance.\n* New SQL/JSON capabilities, including constructors, identity\n  functions, and the JSON_TABLE() function, which converts JSON\n  data into a table representation.\n* Various query performance improvements, including for\n  sequential reads using streaming I/O, write throughput under\n  high concurrency, and searches over multiple values in a btree\n  index.\n* Logical replication enhancements, including:\n  + Failover control\n  + pg_createsubscriber, a utility that creates logical replicas\n    from physical standbys\n  + pg_upgrade now preserves replication slots on both publishers\n    and subscribers\n* New client-side connection option, sslnegotiation=direct, that\n  performs a direct TLS handshake to avoid a round-trip\n  negotiation.\n* pg_basebackup now supports incremental backup.\n* COPY adds a new option, ON_ERROR ignore, that allows a copy\n  operation to continue in the event of an error.\n* https://www.postgresql.org/about/news/p-2936/\n* https://www.postgresql.org/docs/17/release-17.html\n","status":"published","published":"2024-11-25T16:10:37Z","modified":"2026-02-04T10:18:52.599499Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4063-1","title":"Security update for postgresql, postgresql16, postgresql17","description":"This update for postgresql, postgresql16, postgresql17 fixes the following issues:\n\nThis update ships postgresql17 , and fixes security issues with postgresql16:\n\n- bsc#1230423: Relax the dependency of extensions on the server\n  version from exact major.minor to greater or equal, after Tom\n  Lane confirmed on the PostgreSQL packagers list that ABI\n  stability is being taken care of between minor releases.\n\n- bsc#1219340: The last fix was not correct. Improve it by removing\n  the dependency again and call fillup only if it is installed.\n\npostgresql16 was updated to 16.6:\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n* https://www.postgresql.org/docs/release/16.6/\n\npostgresql16 was updated to 16.5:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/16.5/\n\n- Don't build the libs and mini flavor anymore to hand over to\n  PostgreSQL 17.\n\n  * https://www.postgresql.org/about/news/p-2910/\n\npostgresql17 is shipped in version 17.2:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/17.1/\n* https://www.postgresql.org/docs/release/17.2/\n\nUpgrade to 17.2:\n\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n\nUpgrade to 17.0:\n\n* New memory management system for VACUUM, which reduces memory\n  consumption and can improve overall vacuuming performance.\n* New SQL/JSON capabilities, including constructors, identity\n  functions, and the JSON_TABLE() function, which converts JSON\n  data into a table representation.\n* Various query performance improvements, including for\n  sequential reads using streaming I/O, write throughput under\n  high concurrency, and searches over multiple values in a btree\n  index.\n* Logical replication enhancements, including:\n  + Failover control\n  + pg_createsubscriber, a utility that creates logical replicas\n    from physical standbys\n  + pg_upgrade now preserves replication slots on both publishers\n    and subscribers\n* New client-side connection option, sslnegotiation=direct, that\n  performs a direct TLS handshake to avoid a round-trip\n  negotiation.\n* pg_basebackup now supports incremental backup.\n* COPY adds a new option, ON_ERROR ignore, that allows a copy\n  operation to continue in the event of an error.\n* https://www.postgresql.org/about/news/p-2936/\n* https://www.postgresql.org/docs/17/release-17.html\n","status":"published","published":"2024-11-26T09:16:07Z","modified":"2026-02-04T02:39:27.050251Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4095-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-28T12:23:58Z","modified":"2026-02-04T04:36:03.523974Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4096-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-28T12:24:08Z","modified":"2026-02-04T03:12:22.426034Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4097-1","title":"Security update for postgresql12","description":"This update for postgresql12 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-28T12:24:18Z","modified":"2026-02-04T02:31:01.297253Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4098-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-28T12:24:30Z","modified":"2026-02-04T03:35:57.527627Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4099-1","title":"Security update for postgresql12","description":"This update for postgresql12 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-28T12:25:11Z","modified":"2025-05-02T04:36:13.256611Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4114-1","title":"Security update for postgresql13","description":"This update for postgresql13 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-29T09:26:32Z","modified":"2026-02-04T02:51:13.122001Z","updated_at":"2026-11-02T15:53:55.639015Z"},{"id":"SUSE-SU-2024:4118-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-11-29T16:23:57Z","modified":"2026-02-04T02:16:35.14127Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2024:4173-1","title":"Security update for postgresql, postgresql16, postgresql17","description":"This update for postgresql, postgresql16, postgresql17 fixes the following issues:\n\nThis update ships postgresql17 , and fixes security issues with postgresql16:\n\n- bsc#1230423: Relax the dependency of extensions on the server\n  version from exact major.minor to greater or equal, after Tom\n  Lane confirmed on the PostgreSQL packagers list that ABI\n  stability is being taken care of between minor releases.\n\n- bsc#1219340: The last fix was not correct. Improve it by removing\n  the dependency again and call fillup only if it is installed.\n\npostgresql16 was updated to 16.6:\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n* https://www.postgresql.org/docs/release/16.6/\n\npostgresql16 was updated to 16.5:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/16.5/\n\n- Don't build the libs and mini flavor anymore to hand over to\n  PostgreSQL 17.\n\n  * https://www.postgresql.org/about/news/p-2910/\n\npostgresql17 is shipped in version 17.2:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/17.1/\n* https://www.postgresql.org/docs/release/17.2/\n\nUpgrade to 17.2:\n\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n\nUpgrade to 17.0:\n\n* New memory management system for VACUUM, which reduces memory\n  consumption and can improve overall vacuuming performance.\n* New SQL/JSON capabilities, including constructors, identity\n  functions, and the JSON_TABLE() function, which converts JSON\n  data into a table representation.\n* Various query performance improvements, including for\n  sequential reads using streaming I/O, write throughput under\n  high concurrency, and searches over multiple values in a btree\n  index.\n* Logical replication enhancements, including:\n  + Failover control\n  + pg_createsubscriber, a utility that creates logical replicas\n    from physical standbys\n  + pg_upgrade now preserves replication slots on both publishers\n    and subscribers\n* New client-side connection option, sslnegotiation=direct, that\n  performs a direct TLS handshake to avoid a round-trip\n  negotiation.\n* pg_basebackup now supports incremental backup.\n* COPY adds a new option, ON_ERROR ignore, that allows a copy\n  operation to continue in the event of an error.\n* https://www.postgresql.org/about/news/p-2936/\n* https://www.postgresql.org/docs/17/release-17.html\n","status":"published","published":"2024-12-04T14:48:21Z","modified":"2026-02-04T02:22:17.411265Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2024:4174-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-12-04T14:50:14Z","modified":"2026-02-04T04:15:56.628391Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2024:4175-1","title":"Security update for postgresql13","description":"This update for postgresql13 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-12-04T14:51:57Z","modified":"2026-02-04T03:25:03.1394Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2024:4176-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323).\n- CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325).\n- CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326).\n- CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327).\n","status":"published","published":"2024-12-04T14:53:35Z","modified":"2025-05-02T04:36:13.632172Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"SUSE-SU-2025:01799-1","title":"Security update for postgresql, postgresql16, postgresql17","description":"This update for postgresql, postgresql16, postgresql17 fixes the following issues:\n\nThis update ships postgresql17 , and fixes security issues with postgresql16:\n\n- bsc#1230423: Relax the dependency of extensions on the server\n  version from exact major.minor to greater or equal, after Tom\n  Lane confirmed on the PostgreSQL packagers list that ABI\n  stability is being taken care of between minor releases.\n\n- bsc#1219340: The last fix was not correct. Improve it by removing\n  the dependency again and call fillup only if it is installed.\n\npostgresql16 was updated to 16.6:\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n* https://www.postgresql.org/docs/release/16.6/\n\npostgresql16 was updated to 16.5:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/16.5/\n\n- Don't build the libs and mini flavor anymore to hand over to\n  PostgreSQL 17.\n\n  * https://www.postgresql.org/about/news/p-2910/\n\npostgresql17 is shipped in version 17.2:\n\n* CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as\n  dependent on the calling role when RLS applies to a\n  non-top-level table reference.\n* CVE-2024-10977, bsc#1233325: Make libpq discard error messages\n  received during SSL or GSS protocol negotiation.\n* CVE-2024-10978, bsc#1233326: Fix unintended interactions\n  between SET SESSION AUTHORIZATION and SET ROLE\n* CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from\n  changing environment variables.\n* https://www.postgresql.org/about/news/p-2955/\n* https://www.postgresql.org/docs/release/17.1/\n* https://www.postgresql.org/docs/release/17.2/\n\nUpgrade to 17.2:\n\n* Repair ABI break for extensions that work with struct\n  ResultRelInfo.\n* Restore functionality of ALTER {ROLE|DATABASE} SET role.\n* Fix cases where a logical replication slot's restart_lsn could\n  go backwards.\n* Avoid deleting still-needed WAL files during pg_rewind.\n* Fix race conditions associated with dropping shared statistics\n  entries.\n* Count index scans in contrib/bloom indexes in the statistics\n  views, such as the pg_stat_user_indexes.idx_scan counter.\n* Fix crash when checking to see if an index's opclass options\n  have changed.\n* Avoid assertion failure caused by disconnected NFA sub-graphs\n  in regular expression parsing.\n\nUpgrade to 17.0:\n\n* New memory management system for VACUUM, which reduces memory\n  consumption and can improve overall vacuuming performance.\n* New SQL/JSON capabilities, including constructors, identity\n  functions, and the JSON_TABLE() function, which converts JSON\n  data into a table representation.\n* Various query performance improvements, including for\n  sequential reads using streaming I/O, write throughput under\n  high concurrency, and searches over multiple values in a btree\n  index.\n* Logical replication enhancements, including:\n  + Failover control\n  + pg_createsubscriber, a utility that creates logical replicas\n    from physical standbys\n  + pg_upgrade now preserves replication slots on both publishers\n    and subscribers\n* New client-side connection option, sslnegotiation=direct, that\n  performs a direct TLS handshake to avoid a round-trip\n  negotiation.\n* pg_basebackup now supports incremental backup.\n* COPY adds a new option, ON_ERROR ignore, that allows a copy\n  operation to continue in the event of an error.\n* https://www.postgresql.org/about/news/p-2936/\n* https://www.postgresql.org/docs/17/release-17.html\n","status":"published","published":"2025-06-02T13:28:47Z","modified":"2026-02-04T02:17:46.953468Z","updated_at":"2026-11-02T15:53:56.123059Z"},{"id":"USN-7132-1","title":"postgresql-12, postgresql-14, postgresql-16 vulnerabilities","description":"It was discovered that PostgreSQL incorrectly tracked tables with row\nsecurity. A remote attacker could possibly use this issue to perform\nforbidden reads and modifications. (CVE-2024-10976)\n\nJacob Champion discovered that PostgreSQL clients used untrusted server\nerror messages. An attacker that is able to intercept network\ncommunications could possibly use this issue to inject error messages that\ncould be interpreted as valid query results. (CVE-2024-10977)\n\nTom Lane discovered that PostgreSQL incorrectly handled certain privilege\nassignments. A remote attacker could possibly use this issue to view or\nchange different rows from those intended. (CVE-2024-10978)\n\nCoby Abrams discovered that PostgreSQL incorrectly handled environment\nvariables. A remote attacker could possibly use this issue to execute\narbitrary code. (CVE-2024-10979)\n","status":"published","published":"2024-12-02T12:30:50Z","modified":"2026-04-27T17:36:36.247979Z","updated_at":"2026-11-02T16:58:18.876384Z"},{"id":"USN-7358-1","title":"postgresql-9.5 vulnerabilities","description":"Wolfgang Walther discovered that PostgreSQL incorrectly tracked tables with\nrow security. A remote attacker could possibly use this issue to perform\nforbidden reads and modifications. (CVE-2024-10976)\n\nJacob Champion discovered that PostgreSQL clients used untrusted server\nerror messages. An attacker that is able to intercept network\ncommunications could possibly use this issue to inject error messages that\ncould be interpreted as valid query results. (CVE-2024-10977)\n\nTom Lane discovered that PostgreSQL incorrectly handled certain privilege\nassignments. A remote attacker could possibly use this issue to view or\nchange different rows from those intended. (CVE-2024-10978)\n\nCoby Abrams discovered that PostgreSQL incorrectly handled environment\nvariables. A remote attacker could possibly use this issue to execute\narbitrary code. (CVE-2024-10979)\n","status":"published","published":"2025-03-19T12:15:54Z","modified":"2026-06-25T13:32:08.20475278Z","updated_at":"2026-11-02T16:58:19.988474Z"}]}}