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.

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.

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 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.

PostgreSQL Project reports :

This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. Before this fix, any member of a ROLE was able to grant others access to the same ROLE regardless if the member was given the WITH ADMIN OPTION permission. It also fixes multiple privilege escalation issues, including: CVE-2014-0061, CVE-2014-0062, CVE-2014-0063, CVE-2014-0064, CVE-2014-0065, and CVE-2014-0066. More information on these issues can be found on our security page and the security issue detail wiki page.

With this release, we are also alerting users to a known security hole that allows other users on the same machine to gain access to an operating system account while it is doing 'make check' :
CVE-2014-0067. 'Make check' is normally part of building PostgreSQL from source code. As it is not possible to fix this issue without causing significant issues to our testing infrastructure, a patch will be released separately and publicly. Until then, users are strongly advised not to run 'make check' on machines where untrusted users have accounts.

The PostgreSQL database server was updated to version 9.1.12 to fix various security issues :

  - 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)

The complete list of bugs and more information can be found at:
http://www.postgresql.org/docs/9.1/static/release-9-1-12.html

The remote host is running a version of Mac OS X 10.10.x that is prior to 10.10.5. It is, therefore, affected by multiple vulnerabilities in the following components :

  - apache
  - apache_mod_php
  - Apple ID OD Plug-in
  - AppleGraphicsControl
  - Bluetooth
  - bootp
  - CloudKit
  - CoreMedia Playback
  - CoreText
  - curl
  - Data Detectors Engine
  - Date & Time pref pane
  - Dictionary Application
  - DiskImages
  - dyld
  - FontParser
  - groff
  - ImageIO
  - Install Framework Legacy
  - IOFireWireFamily
  - IOGraphics
  - IOHIDFamily
  - Kernel
  - Libc
  - Libinfo
  - libpthread
  - libxml2
  - libxpc
  - mail_cmds
  - Notification Center OSX
  - ntfs
  - OpenSSH
  - OpenSSL
  - perl
  - PostgreSQL
  - python
  - QL Office
  - Quartz Composer Framework
  - Quick Look
  - QuickTime 7
  - SceneKit
  - Security
  - SMBClient
  - Speech UI
  - sudo
  - tcpdump
  - Text Formats
  - udf 

Note that successful exploitation of the most serious issues can result in arbitrary code execution.

The version of PostgreSQL installed on the remote host is 9.0.x prior to 9.0.19, 9.1.x prior to 9.1.15, 9.2.x prior to 9.2.10, 9.3.x prior to 9.3.6, or 9.4.x prior to 9.4.1. It is, therefore, affected by multiple vulnerabilities :

  - A privilege escalation vulnerability exists due to the     'make check' command not properly invoking initdb to     specify authentication requirements for a database     cluster to be used for tests. A local attacker can     exploit this issue to gain temporary server access and     elevated privileges. Note that this issue only affects     Microsoft Windows hosts. (CVE-2014-0067)

  - An information disclosure vulnerability exists due to     improper handling of restricted column values in     constraint-violation error messages. An authenticated,     remote attacker can exploit this to gain access to     sensitive information. (CVE-2014-8161)

  - Multiple vulnerabilities exist due to several buffer     overflow errors related to the 'to_char' functions. An     authenticated, remote attacker can exploit these issues     to cause a denial of service or arbitrary code     execution. (CVE-2015-0241)

  - Multiple vulnerabilities exist due to several     stack-based buffer overflow errors in various *printf()     functions. The overflows are due to improper validation     of user-supplied input when formatting a floating point     number where the requested precision is greater than     approximately 500. An authenticated, remote attacker     can exploit these issues to cause a denial of service or     arbitrary code execution. (CVE-2015-0242)

  - Multiple vulnerabilities exist due to an overflow     condition in multiple functions in the 'pgcrypto'     extension. The overflows are due to improper validation     of user-supplied input when tracking memory sizes. An     authenticated, remote attacker can exploit these issues     to cause a denial of service or arbitrary code     execution. (CVE-2015-0243)

  - A SQL injection vulnerability exists due to improper     sanitization of user-supplied input when handling     crafted binary data within a command parameter. An     authenticated, remote attacker can exploit this issue     to inject or manipulate SQL queries, allowing the     manipulation or disclosure of arbitrary data.
    (CVE-2015-0244)

A buffer overflow flaw was found in the way PostgreSQL handled certain numeric formatting. An authenticated database user could use a specially crafted timestamp formatting template to cause PostgreSQL to crash or, under certain conditions, execute arbitrary code with the permissions of the user running PostgreSQL. (CVE-2015-0241)

A buffer overflow flaw was found in the PostgreSQL's internal printf() implementation. An authenticated database user could use a specially crafted string in a SQL query to cause PostgreSQL to crash or, potentially, lead to privilege escalation. (CVE-2015-0242)

A stack-buffer overflow flaw was found in PostgreSQL's pgcrypto module. An authenticated database user could use this flaw to cause PostgreSQL to crash or, potentially, execute arbitrary code with the permissions of the user running PostgreSQL. (CVE-2015-0243)

A flaw was found in way PostgreSQL handled certain errors during that were generated during protocol synchronization. An authenticated database user could use this flaw to inject queries into an existing connection. (CVE-2015-0244)

The 'make check' command for the test suites in PostgreSQL 9.3.3 and earlier does not properly invoke initdb to specify the authentication requirements for a database cluster to be used for the tests, which allows local users to gain privileges by leveraging access to this cluster. (CVE-2014-0067)

An information leak flaw was found in the way certain the PostgreSQL database server handled certain error messages. An authenticated database user could possibly obtain the results of a query they did not have privileges to execute by observing the constraint violation error messages produced when the query was executed. (CVE-2014-8161)

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
72611	Debian DSA-2865-1 : postgresql-9.1 - several vulnerabilities	Nessus	Debian Local Security Checks	2014/2/21	2021/1/11	medium
72642	Mandriva Linux Security Advisory : postgresql (MDVSA-2014:047)	Nessus	Mandriva Local Security Checks	2014/2/23	2021/1/6	medium
72610	Debian DSA-2864-1 : postgresql-8.4 - several vulnerabilities	Nessus	Debian Local Security Checks	2014/2/21	2021/1/11	medium
72612	FreeBSD : PostgreSQL -- multiple privilege issues (42d42090-9a4d-11e3-b029-08002798f6ff)	Nessus	FreeBSD Local Security Checks	2014/2/21	2021/1/6	medium
73268	SuSE 11.3 Security Update : PostgreSQL 9.1 (SAT Patch Number 8970)	Nessus	SuSE Local Security Checks	2014/3/31	2021/1/19	medium
85408	Mac OS X 10.10.x < 10.10.5 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	2015/8/17	2024/5/28	high
81300	PostgreSQL 9.0 < 9.0.19 / 9.1 < 9.1.15 / 9.2 < 9.2.10 / 9.3 < 9.3.6 / 9.4 < 9.4.1 Multiple Vulnerabilities	Nessus	Databases	2015/2/11	2026/1/22	high
81828	Amazon Linux AMI : postgresql92 (ALAS-2015-492)	Nessus	Amazon Linux Local Security Checks	2015/3/17	2020/2/3	critical

检测

插件搜索

medium

medium

medium

medium

medium

high

high

critical