Updated postgresql packages fix multiple security vulnerabilities :

Granting a role without ADMIN OPTION is supposed to prevent the grantee from adding or removing members from the granted role, but this restriction was easily bypassed by doing SET ROLE first. The security impact is mostly that a role member can revoke the access of others, contrary to the wishes of his grantor. Unapproved role member additions are a lesser concern, since an uncooperative role member could provide most of his rights to others anyway by creating views or SECURITY DEFINER functions (CVE-2014-0060).

The primary role of PL validator functions is to be called implicitly during CREATE FUNCTION, but they are also normal SQL functions that a user can call explicitly. Calling a validator on a function actually written in some other language was not checked for and could be exploited for privilege-escalation purposes. The fix involves adding a call to a privilege-checking function in each validator function.
Non-core procedural languages will also need to make this change to their own validator functions, if any (CVE-2014-0061).

If the name lookups come to different conclusions due to concurrent activity, we might perform some parts of the DDL on a different table than other parts. At least in the case of CREATE INDEX, this can be used to cause the permissions checks to be performed against a different table than the index creation, allowing for a privilege escalation attack (CVE-2014-0062).

The MAXDATELEN constant was too small for the longest possible value of type interval, allowing a buffer overrun in interval_out().
Although the datetime input functions were more careful about avoiding buffer overrun, the limit was short enough to cause them to reject some valid inputs, such as input containing a very long timezone name.
The ecpg library contained these vulnerabilities along with some of its own (CVE-2014-0063).

Several functions, mostly type input functions, calculated an allocation size without checking for overflow. If overflow did occur, a too-small buffer would be allocated and then written past (CVE-2014-0064).

Use strlcpy() and related functions to provide a clear guarantee that fixed-size buffers are not overrun. Unlike the preceding items, it is unclear whether these cases really represent live issues, since in most cases there appear to be previous constraints on the size of the input string. Nonetheless it seems prudent to silence all Coverity warnings of this type (CVE-2014-0065).

There are relatively few scenarios in which crypt() could return NULL, but contrib/chkpass would crash if it did. One practical case in which this could be an issue is if libc is configured to refuse to execute unapproved hashing algorithms (e.g., FIPS mode) (CVE-2014-0066).

Since the temporary server started by make check uses trust authentication, another user on the same machine could connect to it as database superuser, and then potentially exploit the privileges of the operating-system user who started the tests. A future release will probably incorporate changes in the testing procedure to prevent this risk, but some public discussion is needed first. So for the moment, just warn people against using make check when there are untrusted users on the same machine (CVE-2014-0067).

A user with limited clearance on a table might have access to information in columns without SELECT rights on through server error messages (CVE-2014-8161).

The function to_char() might read/write past the end of a buffer. This might crash the server when a formatting template is processed (CVE-2015-0241).

The pgcrypto module is vulnerable to stack buffer overrun that might crash the server (CVE-2015-0243).

Emil Lenngren reported that an attacker can inject SQL commands when the synchronization between client and server is lost (CVE-2015-0244).

This update provides PostgreSQL versions 9.3.6 and 9.2.10 that fix these issues, as well as several others.

The remote MiracleLinux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2014-235:01 advisory.

    PostgreSQL is an advanced Object-Relational database management system (DBMS) that supports almost all SQL     constructs (including transactions, subselects and user-defined types and functions). The postgresql     package includes the client programs and libraries that you'll need to access a PostgreSQL DBMS server.
    These PostgreSQL client programs are programs that directly manipulate the internal structure of     PostgreSQL databases on a PostgreSQL server. These client programs can be located on the same machine with     the PostgreSQL server, or may be on a remote machine which accesses a PostgreSQL server over a network     connection. This package contains the docs in HTML for the whole package, as well as command-line     utilities for managing PostgreSQL databases on a PostgreSQL server.
    If you want to manipulate a PostgreSQL database on a local or remote PostgreSQL server, you need this     package. You also need to install this package if you're installing the postgresql-server package.
    Security issues fixed with this release:
     CVE-2014-0060     PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before     9.3.3 does not properly enforce the ADMIN OPTION restriction, which allows remote authenticated members of     a role to add or remove arbitrary users to that role by calling the SET ROLE command before the associated     GRANT command.
     CVE-2014-0061     The validator functions for the procedural languages (PLs) in PostgreSQL before 8.4.20, 9.0.x before     9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users     to gain privileges via a function that is (1) defined in another language or (2) not allowed to be     directly called by the user due to permissions.
     CVE-2014-0062     No information available at the time of writing, please refer to the CVE link provided below.
     CVE-2014-0063     Multiple stack-based buffer overflows in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before     9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to cause a denial of     service (crash) or possibly execute arbitrary code via vectors related to an incorrect MAXDATELEN constant     and datetime values involving (1) intervals, (2) timestamps, or (3) timezones, a different vulnerability     than CVE-2014-0065.
     CVE-2014-0064     Multiple integer overflows in the path_in and other unspecified functions in PostgreSQL before 8.4.20,     9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote     authenticated users to have unspecified impact and attack vectors, which trigger a buffer overflow. NOTE:
    this identifier has been SPLIT due to different affected versions; use CVE-2014-2669 for the hstore     vector.
     CVE-2014-0065     Multiple buffer overflows in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x     before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to have unspecified impact and     attack vectors, a different vulnerability than CVE-2014-0063.
     CVE-2014-0066     The chkpass extension in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before     9.2.7, and 9.3.x before 9.3.3 does not properly check the return value of the crypt library function,     which allows remote authenticated users to cause a denial of service (NULL pointer dereference and crash)     via unspecified vectors.

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Multiple vulnerabilities has been discovered and corrected in postgresql :

Granting a role without ADMIN OPTION is supposed to prevent the grantee from adding or removing members from the granted role, but this restriction was easily bypassed by doing SET ROLE first. The security impact is mostly that a role member can revoke the access of others, contrary to the wishes of his grantor. Unapproved role member additions are a lesser concern, since an uncooperative role member could provide most of his rights to others anyway by creating views or SECURITY DEFINER functions (CVE-2014-0060).

The primary role of PL validator functions is to be called implicitly during CREATE FUNCTION, but they are also normal SQL functions that a user can call explicitly. Calling a validator on a function actually written in some other language was not checked for and could be exploited for privilege-escalation purposes. The fix involves adding a call to a privilege-checking function in each validator function.
Non-core procedural languages will also need to make this change to their own validator functions, if any (CVE-2014-0061).

If the name lookups come to different conclusions due to concurrent activity, we might perform some parts of the DDL on a different table than other parts. At least in the case of CREATE INDEX, this can be used to cause the permissions checks to be performed against a different table than the index creation, allowing for a privilege escalation attack (CVE-2014-0062).

The MAXDATELEN constant was too small for the longest possible value of type interval, allowing a buffer overrun in interval_out().
Although the datetime input functions were more careful about avoiding buffer overrun, the limit was short enough to cause them to reject some valid inputs, such as input containing a very long timezone name.
The ecpg library contained these vulnerabilities along with some of its own (CVE-2014-0063).

Several functions, mostly type input functions, calculated an allocation size without checking for overflow. If overflow did occur, a too-small buffer would be allocated and then written past (CVE-2014-0064).

Use strlcpy() and related functions to provide a clear guarantee that fixed-size buffers are not overrun. Unlike the preceding items, it is unclear whether these cases really represent live issues, since in most cases there appear to be previous constraints on the size of the input string. Nonetheless it seems prudent to silence all Coverity warnings of this type (CVE-2014-0065).

There are relatively few scenarios in which crypt() could return NULL, but contrib/chkpass would crash if it did. One practical case in which this could be an issue is if libc is configured to refuse to execute unapproved hashing algorithms (e.g., FIPS mode) (CVE-2014-0066).

Since the temporary server started by make check uses trust authentication, another user on the same machine could connect to it as database superuser, and then potentially exploit the privileges of the operating-system user who started the tests. A future release will probably incorporate changes in the testing procedure to prevent this risk, but some public discussion is needed first. So for the moment, just warn people against using make check when there are untrusted users on the same machine (CVE-2014-0067).

This advisory provides the latest version of PostgreSQL that is not vulnerable to these issues.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:0221 advisory.

    PostgreSQL is an advanced object-relational database management system     (DBMS).

    Multiple stack-based buffer overflow flaws were found in the date/time     implementation of PostgreSQL. An authenticated database user could provide     a specially crafted date/time value that, when processed, could cause     PostgreSQL to crash or, potentially, execute arbitrary code with the     permissions of the user running PostgreSQL. (CVE-2014-0063)

    Multiple integer overflow flaws, leading to heap-based buffer overflows,     were found in various type input functions in PostgreSQL. An authenticated     database user could possibly use these flaws to crash PostgreSQL or,     potentially, execute arbitrary code with the permissions of the user     running PostgreSQL. (CVE-2014-0064)

    Multiple potential buffer overflow flaws were found in PostgreSQL.
    An authenticated database user could possibly use these flaws to crash     PostgreSQL or, potentially, execute arbitrary code with the permissions of     the user running PostgreSQL. (CVE-2014-0065)

    It was found that granting an SQL role to a database user in a PostgreSQL     database without specifying the ADMIN option allowed the grantee to     remove other users from their granted role. An authenticated database user     could use this flaw to remove a user from an SQL role which they were     granted access to. (CVE-2014-0060)

    A flaw was found in the validator functions provided by PostgreSQL's     procedural languages (PLs). An authenticated database user could possibly     use this flaw to escalate their privileges. (CVE-2014-0061)

    A race condition was found in the way the CREATE INDEX command performed     multiple independent lookups of a table that had to be indexed. An     authenticated database user could possibly use this flaw to escalate their     privileges. (CVE-2014-0062)

    It was found that the chkpass extension of PostgreSQL did not check the     return value of the crypt() function. An authenticated database user could     possibly use this flaw to crash PostgreSQL via a null pointer dereference.
    (CVE-2014-0066)

    Red Hat would like to thank the PostgreSQL project for reporting these     issues. Upstream acknowledges Noah Misch as the original reporter of     CVE-2014-0060 and CVE-2014-0063, Heikki Linnakangas and Noah Misch as the     original reporters of CVE-2014-0064, Peter Eisentraut and Jozef Mlich as     the original reporters of CVE-2014-0065, Andres Freund as the original     reporter of CVE-2014-0061, Robert Haas and Andres Freund as the original     reporters of CVE-2014-0062, and Honza Horak and Bruce Momjian as the     original reporters of CVE-2014-0066.

    These updated packages upgrade PostgreSQL to version 9.2.7, which fixes     these issues as well as several non-security issues. Refer to the     PostgreSQL Release Notes for a full list of changes:

    http://www.postgresql.org/docs/9.2/static/release-9-2-7.html

    All PostgreSQL users are advised to upgrade to these updated packages,     which contain backported patches to correct these issues. If the postgresql     service is running, it will be automatically restarted after installing     this update.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Various vulnerabilities were discovered in PostgreSQL :

  - CVE-2014-0060 Shore up GRANT ... WITH ADMIN OPTION     restrictions (Noah Misch)     Granting a role without ADMIN OPTION is supposed to     prevent the grantee from adding or removing members from     the granted role, but this restriction was easily     bypassed by doing SET ROLE first. The security impact is     mostly that a role member can revoke the access of     others, contrary to the wishes of his grantor.
    Unapproved role member additions are a lesser concern,     since an uncooperative role member could provide most of     his rights to others anyway by creating views or     SECURITY DEFINER functions.

  - CVE-2014-0061 Prevent privilege escalation via manual     calls to PL validator functions (Andres Freund)

    The primary role of PL validator functions is to be     called implicitly during CREATE FUNCTION, but they are     also normal SQL functions that a user can call     explicitly. Calling a validator on a function actually     written in some other language was not checked for and     could be exploited for privilege-escalation purposes.
    The fix involves adding a call to a privilege-checking     function in each validator function. Non-core procedural     languages will also need to make this change to their     own validator functions, if any.

  - CVE-2014-0062 Avoid multiple name lookups during table     and index DDL (Robert Haas, Andres Freund)

    If the name lookups come to different conclusions due to     concurrent activity, we might perform some parts of the     DDL on a different table than other parts. At least in     the case of CREATE INDEX, this can be used to cause the     permissions checks to be performed against a different     table than the index creation, allowing for a privilege     escalation attack.

  - CVE-2014-0063 Prevent buffer overrun with long datetime     strings (Noah Misch)

    The MAXDATELEN constant was too small for the longest     possible value of type interval, allowing a buffer     overrun in interval_out(). Although the datetime input     functions were more careful about avoiding buffer     overrun, the limit was short enough to cause them to     reject some valid inputs, such as input containing a     very long timezone name. The ecpg library contained     these vulnerabilities along with some of its own.

  - CVE-2014-0064 CVE-2014-2669 Prevent buffer overrun due     to integer overflow in size calculations (Noah Misch,     Heikki Linnakangas)

    Several functions, mostly type input functions,     calculated an allocation size without checking for     overflow. If overflow did occur, a too-small buffer     would be allocated and then written past.

  - CVE-2014-0065 Prevent overruns of fixed-size buffers     (Peter Eisentraut, Jozef Mlich)

    Use strlcpy() and related functions to provide a clear     guarantee that fixed-size buffers are not overrun.
    Unlike the preceding items, it is unclear whether these     cases really represent live issues, since in most cases     there appear to be previous constraints on the size of     the input string. Nonetheless it seems prudent to     silence all Coverity warnings of this type.

  - CVE-2014-0066 Avoid crashing if crypt() returns NULL     (Honza Horak, Bruce Momjian)

    There are relatively few scenarios in which crypt()     could return NULL, but contrib/chkpass would crash if it     did. One practical case in which this could be an issue     is if libc is configured to refuse to execute unapproved     hashing algorithms (e.g., 'FIPS mode').

  - CVE-2014-0067 Document risks of make check in the     regression testing instructions (Noah Misch, Tom Lane)

    Since the temporary server started by make check uses     'trust' authentication, another user on the same machine     could connect to it as database superuser, and then     potentially exploit the privileges of the     operating-system user who started the tests. A future     release will probably incorporate changes in the testing     procedure to prevent this risk, but some public     discussion is needed first. So for the moment, just warn     people against using make check when there are untrusted     users on the same machine.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
82363	Mandriva Linux Security Advisory : postgresql (MDVSA-2015:110)	Nessus	Mandriva Local Security Checks	2015/3/30	2021/1/14	medium
289133	MiracleLinux 3 : postgresql-8.1.23-10.0.1.AXS3 (AXSA:2014-235:01)	Nessus	Miracle Linux Local Security Checks	2026/1/16	2026/1/16	critical
72642	Mandriva Linux Security Advisory : postgresql (MDVSA-2014:047)	Nessus	Mandriva Local Security Checks	2014/2/23	2021/1/6	medium
210204	RHEL 6 : postgresql92-postgresql (RHSA-2014:0221)	Nessus	Red Hat Local Security Checks	2024/11/4	2024/11/4	critical
72611	Debian DSA-2865-1 : postgresql-9.1 - several vulnerabilities	Nessus	Debian Local Security Checks	2014/2/21	2021/1/11	medium

检测

插件搜索

medium

critical

medium

critical

medium