RHSA-2018:2511: Important: rh-postgresql95-postgresql security update
PostgreSQL is an advanced object-relational database management system (DBMS).The following packages have been upgraded to a later upstream version: rh-postgresql95-postgresql (9.5.14). (BZ#1612671)Security Fix(es): postgresql: Certain host connection parameters defeat client-side security defenses (CVE-2018-10915) postgresql: Missing authorization and memory disclosure in INSERT ... ON CONFLICT DO UPDATE statements (CVE-2018-10925) postgresql: Memory disclosure in JSON functions (CVE-2017-15098) postgresql: pgupgrade creates file of sensitive metadata under prevailing umask (CVE-2018-1053) postgresql: Uncontrolled search path element in pgdump and other client applications (CVE-2018-1058) postgresql: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges (CVE-2017-15099) For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.Red Hat would like to thank the PostgreSQL project for reporting CVE-2018-10915, CVE-2018-10925, CVE-2017-15098, CVE-2018-1053, and CVE-2017-15099. Upstream acknowledges Andrew Krasichkov as the original reporter of CVE-2018-10915; David Rowley as the original reporter of CVE-2017-15098; Tom Lane as the original reporter of CVE-2018-1053; and Dean Rasheed as the original reporter of CVE-2017-15099.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2018:2511?
The severity of RHSA-2018:2511 is classified as important.
How do I fix RHSA-2018:2511?
To address RHSA-2018:2511, upgrade the affected PostgreSQL packages to version 9.5.14-1.el7 or later.
Which packages are affected by RHSA-2018:2511?
RHSA-2018:2511 affects rh-postgresql95-postgresql, rh-postgresql95-postgresql-contrib, and several other related packages.
What vulnerabilities are addressed in RHSA-2018:2511?
RHSA-2018:2511 addresses multiple vulnerabilities related to host connection parameters in PostgreSQL.
Is there a workaround for RHSA-2018:2511?
While a specific workaround is not provided for RHSA-2018:2511, updating the affected packages is recommended.