https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:30:35 +0000 https://cve.radiocsirt.org/vuln/bdu:2019-04232 bdu:2019-04232 https://cve.radiocsirt.org/vuln/bdu:2019-04232 https://cve.radiocsirt.org/vuln/bell-cve-2018-1053 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2018-1053 https://cve.radiocsirt.org/vuln/cleanstart-2026-sx71048 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: postgresql</p> <p>Package postgresql version 10.2-r0 fixes 2 vulnerabilities: CVE-2018-1052, CVE-2018-1053</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: postgresql</p> <p>Package postgresql version 10.2-r0 fixes 2 vulnerabilities: CVE-2018-1052, CVE-2018-1053</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-sx71048 https://cve.radiocsirt.org/vuln/cnvd-2018-05754 cnvd-2018-05754 https://cve.radiocsirt.org/vuln/cnvd-2018-05754 https://cve.radiocsirt.org/vuln/euvd-2026-185561 EUVD-2026-185561 https://cve.radiocsirt.org/vuln/euvd-2026-185561 https://cve.radiocsirt.org/vuln/fkie_cve-2018-1053 <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-1053 https://cve.radiocsirt.org/vuln/ghsa-h73g-3m4r-j2cr <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> https://cve.radiocsirt.org/vuln/ghsa-h73g-3m4r-j2cr https://cve.radiocsirt.org/vuln/gsd-2018-1053 gsd-2018-1053 https://cve.radiocsirt.org/vuln/gsd-2018-1053 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11184-1 <p>postgresql10-10.18-1.3 on GA media</p> <p>postgresql10-10.18-1.3 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11184-1 https://cve.radiocsirt.org/vuln/rhsa-2018:2511 <p>postgresql: Memory disclosure in JSON functions postgresql: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges postgresql: pg_upgrade creates file of sensitive metadata under prevailing umask postgresql: Uncontrolled search path element in pg_dump and other client applications postgresql: Certain host connection parameters defeat client-side security defenses postgresql: Missing authorization and memory disclosure in INSERT ... ON CONFLICT DO UPDATE statements</p> <p>postgresql: Memory disclosure in JSON functions postgresql: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges postgresql: pg_upgrade creates file of sensitive metadata under prevailing umask postgresql: Uncontrolled search path element in pg_dump and other client applications postgresql: Certain host connection parameters defeat client-side security defenses postgresql: Missing authorization and memory disclosure in INSERT ... ON CONFLICT DO UPDATE statements</p> https://cve.radiocsirt.org/vuln/rhsa-2018:2511 https://cve.radiocsirt.org/vuln/suse-su-2018:0506-1 <p>Security update for postgresql94</p> <p>Security update for postgresql94</p> https://cve.radiocsirt.org/vuln/suse-su-2018:0506-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-1053 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: postgresql-9.3, Ubuntu:16.04:LTS: postgresql-9.5</p> <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: postgresql-9.3, Ubuntu:16.04:LTS: postgresql-9.5</p> <p>In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-1053