ID CVE-2007-6601
Summary The DBLink module in PostgreSQL 8.2 before 8.2.6, 8.1 before 8.1.11, 8.0 before 8.0.15, 7.4 before 7.4.19, and 7.3 before 7.3.21, when local trust or ident authentication is used, allows remote attackers to gain privileges via unspecified vectors. NOTE: this issue exists because of an incomplete fix for CVE-2007-3278.
References
Vulnerable Configurations
  • cpe:2.3:a:postgresql:postgresql:7.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.15:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.15:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.3.19:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.3.19:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.10:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.12:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.12:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.14:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.14:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.16:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.16:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:7.4.17:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:7.4.17:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.0.317:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.0.317:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.1.9:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:postgresql:postgresql:8.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:postgresql:postgresql:8.2.4:*:*:*:*:*:*:*
CVSS
Base: 7.2 (as of 15-10-2018 - 21:55)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
LOCAL LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
cvss-vector via4 AV:L/AC:L/Au:N/C:C/I:C/A:C
oval via4
accepted 2013-04-29T04:11:41.689-04:00
class vulnerability
contributors
  • name Aharon Chernin
    organization SCAP.com, LLC
  • name Dragos Prisaca
    organization G2, Inc.
definition_extensions
  • comment The operating system installed on the system is Red Hat Enterprise Linux 3
    oval oval:org.mitre.oval:def:11782
  • comment CentOS Linux 3.x
    oval oval:org.mitre.oval:def:16651
  • comment The operating system installed on the system is Red Hat Enterprise Linux 4
    oval oval:org.mitre.oval:def:11831
  • comment CentOS Linux 4.x
    oval oval:org.mitre.oval:def:16636
  • comment Oracle Linux 4.x
    oval oval:org.mitre.oval:def:15990
  • comment The operating system installed on the system is Red Hat Enterprise Linux 5
    oval oval:org.mitre.oval:def:11414
  • comment The operating system installed on the system is CentOS Linux 5.x
    oval oval:org.mitre.oval:def:15802
  • comment Oracle Linux 5.x
    oval oval:org.mitre.oval:def:15459
description The DBLink module in PostgreSQL 8.2 before 8.2.6, 8.1 before 8.1.11, 8.0 before 8.0.15, 7.4 before 7.4.19, and 7.3 before 7.3.21, when local trust or ident authentication is used, allows remote attackers to gain privileges via unspecified vectors. NOTE: this issue exists because of an incomplete fix for CVE-2007-3278.
family unix
id oval:org.mitre.oval:def:11127
status accepted
submitted 2010-07-09T03:56:16-04:00
title The DBLink module in PostgreSQL 8.2 before 8.2.6, 8.1 before 8.1.11, 8.0 before 8.0.15, 7.4 before 7.4.19, and 7.3 before 7.3.21, when local trust or ident authentication is used, allows remote attackers to gain privileges via unspecified vectors. NOTE: this issue exists because of an incomplete fix for CVE-2007-3278.
version 24
redhat via4
advisories
  • bugzilla
    id 427128
    title CVE-2007-6601 PostgreSQL privilege escalation via dblink
    oval
    OR
    • AND
      • comment Red Hat Enterprise Linux 4 is installed
        oval oval:com.redhat.rhba:tst:20070304001
      • OR
        • AND
          • comment postgresql is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038002
          • comment postgresql is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064026
        • AND
          • comment postgresql-contrib is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038010
          • comment postgresql-contrib is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064038
        • AND
          • comment postgresql-devel is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038004
          • comment postgresql-devel is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064036
        • AND
          • comment postgresql-docs is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038008
          • comment postgresql-docs is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064046
        • AND
          • comment postgresql-jdbc is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038014
          • comment postgresql-jdbc is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064032
        • AND
          • comment postgresql-libs is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038020
          • comment postgresql-libs is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064030
        • AND
          • comment postgresql-pl is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038006
          • comment postgresql-pl is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064028
        • AND
          • comment postgresql-python is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038016
          • comment postgresql-python is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064044
        • AND
          • comment postgresql-server is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038012
          • comment postgresql-server is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064034
        • AND
          • comment postgresql-tcl is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038022
          • comment postgresql-tcl is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064040
        • AND
          • comment postgresql-test is earlier than 0:7.4.19-1.el4_6.1
            oval oval:com.redhat.rhsa:tst:20080038018
          • comment postgresql-test is signed with Red Hat master key
            oval oval:com.redhat.rhsa:tst:20070064042
    • AND
      • comment Red Hat Enterprise Linux 5 is installed
        oval oval:com.redhat.rhba:tst:20070331001
      • OR
        • AND
          • comment postgresql is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038025
          • comment postgresql is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068003
        • AND
          • comment postgresql-contrib is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038043
          • comment postgresql-contrib is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068013
        • AND
          • comment postgresql-devel is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038027
          • comment postgresql-devel is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068009
        • AND
          • comment postgresql-docs is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038041
          • comment postgresql-docs is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068005
        • AND
          • comment postgresql-libs is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038031
          • comment postgresql-libs is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068011
        • AND
          • comment postgresql-pl is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038037
          • comment postgresql-pl is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068017
        • AND
          • comment postgresql-python is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038033
          • comment postgresql-python is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068015
        • AND
          • comment postgresql-server is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038029
          • comment postgresql-server is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068019
        • AND
          • comment postgresql-tcl is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038035
          • comment postgresql-tcl is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068007
        • AND
          • comment postgresql-test is earlier than 0:8.1.11-1.el5_1.1
            oval oval:com.redhat.rhsa:tst:20080038039
          • comment postgresql-test is signed with Red Hat redhatrelease key
            oval oval:com.redhat.rhsa:tst:20070068021
    rhsa
    id RHSA-2008:0038
    released 2008-01-11
    severity Moderate
    title RHSA-2008:0038: postgresql security update (Moderate)
  • bugzilla
    id 427128
    title CVE-2007-6601 PostgreSQL privilege escalation via dblink
    oval
    AND
    • comment Red Hat Enterprise Linux 3 is installed
      oval oval:com.redhat.rhba:tst:20070026001
    • OR
      • AND
        • comment rh-postgresql is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039002
        • comment rh-postgresql is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064003
      • AND
        • comment rh-postgresql-contrib is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039010
        • comment rh-postgresql-contrib is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064017
      • AND
        • comment rh-postgresql-devel is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039016
        • comment rh-postgresql-devel is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064013
      • AND
        • comment rh-postgresql-docs is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039018
        • comment rh-postgresql-docs is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064009
      • AND
        • comment rh-postgresql-jdbc is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039004
        • comment rh-postgresql-jdbc is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064005
      • AND
        • comment rh-postgresql-libs is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039022
        • comment rh-postgresql-libs is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064011
      • AND
        • comment rh-postgresql-pl is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039014
        • comment rh-postgresql-pl is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064015
      • AND
        • comment rh-postgresql-python is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039006
        • comment rh-postgresql-python is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064019
      • AND
        • comment rh-postgresql-server is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039008
        • comment rh-postgresql-server is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064021
      • AND
        • comment rh-postgresql-tcl is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039020
        • comment rh-postgresql-tcl is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064023
      • AND
        • comment rh-postgresql-test is earlier than 0:7.3.21-1
          oval oval:com.redhat.rhsa:tst:20080039012
        • comment rh-postgresql-test is signed with Red Hat master key
          oval oval:com.redhat.rhsa:tst:20070064007
    rhsa
    id RHSA-2008:0039
    released 2008-01-11
    severity Moderate
    title RHSA-2008:0039: postgresql security update (Moderate)
  • rhsa
    id RHSA-2008:0040
rpms
  • postgresql-0:7.4.19-1.el4_6.1
  • postgresql-contrib-0:7.4.19-1.el4_6.1
  • postgresql-devel-0:7.4.19-1.el4_6.1
  • postgresql-docs-0:7.4.19-1.el4_6.1
  • postgresql-jdbc-0:7.4.19-1.el4_6.1
  • postgresql-libs-0:7.4.19-1.el4_6.1
  • postgresql-pl-0:7.4.19-1.el4_6.1
  • postgresql-python-0:7.4.19-1.el4_6.1
  • postgresql-server-0:7.4.19-1.el4_6.1
  • postgresql-tcl-0:7.4.19-1.el4_6.1
  • postgresql-test-0:7.4.19-1.el4_6.1
  • postgresql-0:8.1.11-1.el5_1.1
  • postgresql-contrib-0:8.1.11-1.el5_1.1
  • postgresql-devel-0:8.1.11-1.el5_1.1
  • postgresql-docs-0:8.1.11-1.el5_1.1
  • postgresql-libs-0:8.1.11-1.el5_1.1
  • postgresql-pl-0:8.1.11-1.el5_1.1
  • postgresql-python-0:8.1.11-1.el5_1.1
  • postgresql-server-0:8.1.11-1.el5_1.1
  • postgresql-tcl-0:8.1.11-1.el5_1.1
  • postgresql-test-0:8.1.11-1.el5_1.1
  • rh-postgresql-0:7.3.21-1
  • rh-postgresql-contrib-0:7.3.21-1
  • rh-postgresql-devel-0:7.3.21-1
  • rh-postgresql-docs-0:7.3.21-1
  • rh-postgresql-jdbc-0:7.3.21-1
  • rh-postgresql-libs-0:7.3.21-1
  • rh-postgresql-pl-0:7.3.21-1
  • rh-postgresql-python-0:7.3.21-1
  • rh-postgresql-server-0:7.3.21-1
  • rh-postgresql-tcl-0:7.3.21-1
  • rh-postgresql-test-0:7.3.21-1
refmap via4
bid 27163
bugtraq
  • 20080107 PostgreSQL 2007-01-07 Cumulative Security Release
  • 20080115 rPSA-2008-0016-1 postgresql postgresql-server
confirm
debian
  • DSA-1460
  • DSA-1463
fedora
  • FEDORA-2008-0478
  • FEDORA-2008-0552
gentoo GLSA-200801-15
hp
  • HPSBTU02325
  • SSRT080006
mandriva MDVSA-2008:004
sectrack 1019157
secunia
  • 28359
  • 28376
  • 28437
  • 28438
  • 28445
  • 28454
  • 28455
  • 28464
  • 28477
  • 28479
  • 28679
  • 28698
  • 29638
sunalert
  • 103197
  • 200559
suse SUSE-SA:2008:005
ubuntu USN-568-1
vupen
  • ADV-2008-0061
  • ADV-2008-0109
  • ADV-2008-1071
xf postgresql-dblink-privilege-escalation(39500)
Last major update 15-10-2018 - 21:55
Published 09-01-2008 - 21:46
Back to Top