Multiple integer overflows in contrib/hstore/hstore_io.c in PostgreSQL 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 via vectors related to the (1) hstore_recv, (2) hstore_from_arrays, and (3) hstore_from_array functions in contrib/hstore/hstore_io.c; and the (4) hstoreArrayToPairs function in contrib/hstore/hstore_op.c, which triggers a buffer overflow. NOTE: this issue was SPLIT from CVE-2014-0064 because it has a different set of affected versions.

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.

The remote host is affected by the vulnerability described in GLSA-201408-15 (PostgreSQL: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in PostgreSQL. Please       review the CVE identifiers referenced below for details.
  Impact :

    A remote authenticated attacker may be able to create a Denial of       Service condition, bypass security restrictions, or have other       unspecified impact.
  Workaround :

    There is no known workaround at this time.

The remote CentOS host is missing a security update which has been documented in Red Hat advisory RHSA-2014:0221.

The version of PostgreSQL installed on the remote host is 8.4.x prior to 8.4.20, 9.0.x prior to 9.0.16, 9.1.x prior to 9.1.12, 9.2.x prior to 9.2.7 or 9.3.x prior to 9.3.3 and is potentially affected by multiple vulnerabilities :

 - SET ROLE bypasses lack of ADMIN OPTION when granting roles. (CVE-2014-0060)

 - It is possible to elevate privileges via calls to validator functions. (CVE-2014-0061)

 - It is possible to elevate privileges via a race condition in CREATE INDEX. (CVE-2014-0062)

 - Potential buffer overruns exist due to integer overflow in size calculations. (CVE-2014-0063)

 - Potential buffer overruns exist in datetime input/output. (CVE-2014-0064)

 - Multiple fixed-size buffers exist that could potentially be overflowed. (CVE-2014-0065)

 - A potential NULL pointer dereference crash is possible when crypt(3) returns NULL. (CVE-2014-0066)

 - Multiple integer overflow vulnerabilities exist in 'hstore_io.c'. (CVE-2014-2669)

The version of PostgreSQL installed on the remote host is 8.4.x prior to 8.4.20, 9.0.x prior to 9.0.16, 9.1.x prior to 9.1.12, 9.2.x prior to 9.2.7 or 9.3.x prior to 9.3.3.  It is, therefore, potentially affected by multiple vulnerabilities :

  - SET ROLE bypasses lack of ADMIN OPTION when granting     roles. (CVE-2014-0060)

  - It is possible to elevate privileges via calls to     validator functions. (CVE-2014-0061)

  - It is possible to elevate privileges via a race     condition in CREATE INDEX. (CVE-2014-0062)

  - Potential buffer overruns exist due to integer overflow     in size calculations. (CVE-2014-0063)

  - Potential buffer overruns exist in datetime     input/output. (CVE-2014-0064)

  - Multiple fixed-size buffers exist that could potentially     be overflowed. (CVE-2014-0065)

  - A potential NULL pointer dereference crash is possible     when crypt(3) returns NULL. (CVE-2014-0066)     
  - Multiple integer overflow vulnerabilities exist in     'hstore_io.c' (CVE-2014-2669)

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	Name	Product	Family	Severity
210204	RHEL 6 : postgresql92-postgresql (RHSA-2014:0221)	Nessus	Red Hat Local Security Checks	critical
77459	GLSA-201408-15 : PostgreSQL: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
72865	CentOS 6 : postgresql92-postgresql (CESA-2014:0221)	Nessus	CentOS Local Security Checks	medium
8133	PostgreSQL 8.4.x < 8.4.20 / 9.0.x < 9.0.16 / 9.1.x < 9.1.12 / 9.2.x < 9.2.7 / 9.3.x < 9.3.3 Multiple Vulnerabilities	Nessus Network Monitor	Database	medium
72659	PostgreSQL 8.4 < 8.4.20 / 9.0 < 9.0.16 / 9.1 < 9.1.12 / 9.2 < 9.2.7 / 9.3 < 9.3.3 Multiple Vulnerabilities	Nessus	Databases	critical
72611	Debian DSA-2865-1 : postgresql-9.1 - several vulnerabilities	Nessus	Debian Local Security Checks	medium

Detections

Analytics

CVE-2014-2669

high

Tenable Plugins

critical

high

medium

medium

critical

medium