ID CVE-2018-10915
Summary A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.
References
Vulnerable Configurations
  • cpe:2.3:a:redhat:openstack:12.0:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openstack:12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openstack:13.0:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openstack:13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:virtualization:4.0:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:virtualization:4.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_desktop:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_desktop:7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_server:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_server:7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_server_eus:7.5:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_server_eus:7.5:*:*:*:*:*:*:*
  • cpe:2.3:o:redhat:enterprise_linux_workstation:7.0:*:*:*:*:*:*:*
    cpe:2.3:o:redhat:enterprise_linux_workstation:7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:lts:*:*:*
    cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
    cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
    cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.20:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.20:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.21:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.21:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.22:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.22:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.3.23:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.3.23:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.4.18:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.4.18:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.5.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.5.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:9.6.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:9.6.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:10.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:10.4:*:*:*:*:*:*:*
CVSS
Base: 6.0 (as of 03-10-2019 - 00:03)
Impact:
Exploitability:
CWE CWE-89
CAPEC
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:
  • Blind SQL Injection
    Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.
Access
VectorComplexityAuthentication
NETWORK MEDIUM SINGLE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:N/AC:M/Au:S/C:P/I:P/A:P
redhat via4
advisories
  • bugzilla
    id 1609891
    title CVE-2018-10915 postgresql: Certain host connection parameters defeat client-side security defenses
    oval
    AND
    • OR
      • comment Red Hat Enterprise Linux 7 Client is installed
        oval oval:com.redhat.rhba:tst:20150364001
      • comment Red Hat Enterprise Linux 7 Server is installed
        oval oval:com.redhat.rhba:tst:20150364002
      • comment Red Hat Enterprise Linux 7 Workstation is installed
        oval oval:com.redhat.rhba:tst:20150364003
      • comment Red Hat Enterprise Linux 7 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20150364004
    • OR
      • AND
        • comment postgresql is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557007
        • comment postgresql is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908006
      • AND
        • comment postgresql-contrib is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557015
        • comment postgresql-contrib is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908014
      • AND
        • comment postgresql-devel is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557025
        • comment postgresql-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908010
      • AND
        • comment postgresql-docs is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557023
        • comment postgresql-docs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908016
      • AND
        • comment postgresql-libs is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557013
        • comment postgresql-libs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908024
      • AND
        • comment postgresql-plperl is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557021
        • comment postgresql-plperl is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908022
      • AND
        • comment postgresql-plpython is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557027
        • comment postgresql-plpython is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908018
      • AND
        • comment postgresql-pltcl is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557017
        • comment postgresql-pltcl is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908020
      • AND
        • comment postgresql-server is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557011
        • comment postgresql-server is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908012
      • AND
        • comment postgresql-static is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557005
        • comment postgresql-static is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20171983026
      • AND
        • comment postgresql-test is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557009
        • comment postgresql-test is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20100908008
      • AND
        • comment postgresql-upgrade is earlier than 0:9.2.24-1.el7_5
          oval oval:com.redhat.rhsa:tst:20182557019
        • comment postgresql-upgrade is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20150750037
    rhsa
    id RHSA-2018:2557
    released 2018-08-23
    severity Important
    title RHSA-2018:2557: postgresql security update (Important)
  • rhsa
    id RHSA-2018:2511
  • rhsa
    id RHSA-2018:2565
  • rhsa
    id RHSA-2018:2566
  • rhsa
    id RHSA-2018:2643
  • rhsa
    id RHSA-2018:2721
  • rhsa
    id RHSA-2018:2729
  • rhsa
    id RHSA-2018:3816
rpms
  • postgresql-0:9.2.24-1.el7_5
  • postgresql-contrib-0:9.2.24-1.el7_5
  • postgresql-devel-0:9.2.24-1.el7_5
  • postgresql-docs-0:9.2.24-1.el7_5
  • postgresql-libs-0:9.2.24-1.el7_5
  • postgresql-plperl-0:9.2.24-1.el7_5
  • postgresql-plpython-0:9.2.24-1.el7_5
  • postgresql-pltcl-0:9.2.24-1.el7_5
  • postgresql-server-0:9.2.24-1.el7_5
  • postgresql-static-0:9.2.24-1.el7_5
  • postgresql-test-0:9.2.24-1.el7_5
  • postgresql-upgrade-0:9.2.24-1.el7_5
refmap via4
bid 105054
confirm
debian DSA-4269
gentoo GLSA-201810-08
mlist [debian-lts-announce] 20180815 [SECURITY] [DLA 1464-1] postgresql-9.4 security update
sectrack 1041446
ubuntu USN-3744-1
Last major update 03-10-2019 - 00:03
Published 09-08-2018 - 20:29
Last modified 17-08-2020 - 19:15
Back to Top