Skip site navigation (1) Skip section navigation (2)

Security Information

If you wish to report a new security vulnerability in PostgreSQL, please send an email to security@postgresql.org. For reporting non-security bugs, please see the Report a Bug page.

The PostgreSQL Global Development Group (PGDG) takes security seriously, allowing our users to place their trust in the web sites and applications built around PostgreSQL. Our approach covers fail-safe configuration options, a secure and robust database server as well as good integration with other security infrastructure software.

PostgreSQL security updates are primarily made available as minor version upgrades. You are always advised to use the latest minor version available, as it will likely also contain other non-security related fixes. All known security issues are always fixed in the next major release, when it comes out.

PGDG believes that accuracy, completeness and availability of security information is essential for our users. We choose to pool all information on this one page, allowing easy searching for vulnerabilities by a range of criteria.

Vulnerabilities list which major releases they were present in, and which version they are fixed in for each. If the vulnerability was exploitable without a valid login, this is also stated. They also list a vulnerability class, but we urge all users to read the description to determine if the bug affects specific installations or not.

Known security issues in all supported versions

You can filter the view of patches to show just patches for version:
10 - 9.6 - 9.5 - 9.4 - 9.3 - all

Reference Affected
versions
Fixed in Component and
CVSS v3 Base Score
Description
CVE-2010-4015
8.2, 8.3, 8.4, 9.0 8.2.20, 8.3.14, 8.4.7, 9.0.3 contrib module
Legacy: C
An authenticated database user can cause a buffer overrun by calling functions from the intarray optional module with certain parameters.
CVE-2010-3433
7.4, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0 7.4.30, 8.0.26, 8.1.22, 8.2.18, 8.3.12, 8.4.5, 9.0.1 core server
Legacy: C
An authenticated database user can manipulate modules and tied variables in some external procedural languages to execute code with enhanced privileges.Details

more details
CVE-2010-1975
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.29, 8.0.25, 8.1.21, 8.2.17, 8.3.11, 8.4.4 core server
Legacy: C
An unprivileged database user can remove superuser-only settings that were applied to his account with ALTER USER by a superuser, thus bypassing settings that should be enforced.
CVE-2010-1170
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.29, 8.0.25, 8.1.21, 8.2.17, 8.3.11, 8.4.4 core server
Legacy: C
Insecure permissions on the pltcl_modules table could allow an authenticated user to run arbitrary Tcl code on the database server if PL/Tcl is installed and enabled.
CVE-2010-1169
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.29, 8.0.25, 8.1.21, 8.2.17, 8.3.11, 8.4.4 core server
Legacy: C
A vulnerability in Safe.pm and PL/Perl can allow an authenticated user to run arbitrary Perl code on the database server if PL/Perl is installed and enabled.
CVE-2009-4136
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.27, 8.0.23, 8.1.19, 8.2.15, 8.3.9, 8.4.2 core server
Legacy: C
Privilege escalation via changing session state in an index function. This closes a corner case related to vulnerabilities CVE-2009-3230 and CVE-2007-6600 (below).
CVE-2009-4034
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.27, 8.0.23, 8.1.19, 8.2.15, 8.3.9, 8.4.2 core server
Legacy: A
NULL Bytes in SSL Certificates can be used to falsify client or server authentication. This only affects users who have SSL enabled, perform certificate name validation or client certificate authentication, and where the Certificate Authority (CA) has been tricked into issuing invalid certificates. The use of a CA that can be trusted to always issue valid certificates is recommended to ensure you are not vulnerable to this issue.
CVE-2009-3231
8.2, 8.3 8.2.14, 8.3.8 core server
Legacy: A
If PostgreSQL is configured with LDAP authentication, and your LDAP configuration allows anonymous binds, it is possible for a user to authenticate themselves with an empty password.
CVE-2009-3230
7.4, 8.0, 8.1, 8.2, 8.3, 8.4 7.4.26, 8.0.22, 8.1.18, 8.2.14, 8.3.8, 8.4.1 core server
Legacy: C
The fix for issue CVE-2007-6600 (below) failed to include protection against misuse of RESET SESSION AUTHORIZATION.
CVE-2009-3229
8.2, 8.3, 8.4 8.2.14, 8.3.8, 8.4.1 core server
Legacy: D
Authenticated non-superusers can shut down the backend server by re-LOAD-ing libraries in $libdir/plugins, if any libraries are present there.
CVE-2009-0922
7.4, 8.0, 8.1, 8.2, 8.3 7.4.25, 8.0.21, 8.1.17, 8.2.13, 8.3.7 core server
Legacy: D
It is possible to cause a momentary denial of service when there is a failure to convert a localized error message to the client-specified encoding. A valid login is required to exploit this vulnerability.
CVE-2007-6601
7.3, 7.4, 8.0, 8.1, 8.2 7.3.21, 7.4.19, 8.0.15, 8.1.11, 8.2.6 contrib module
Legacy: C
DBLink functions combined with local trust or ident access control could be used by a malicious user togain superuser privileges. A valid login is required to exploit this vulnerability.
CVE-2007-6600
7.3, 7.4, 8.0, 8.1, 8.2 7.3.21, 7.4.19, 8.0.15, 8.1.11, 8.2.6 core server
Legacy: C
Two vulnerabilities in how ANALYZE executes user defined functions that are part of expression indexes allows users to gain superuser privileges. A valid login that has permissions to create functions and tables is required to exploit this vulnearbility.
CVE-2007-4769
7.4, 8.0, 8.1, 8.2 7.4.19, 8.0.15, 8.1.11, 8.2.6 core server
Legacy: B
Three vulnearbilities in the regular expression handling libraries can be exploited to cause a backend crash, infinite loops or memory exhaustion. This vulnearbility can be exploited through frontend applications that allow unfiltered regular expressions to be passed in queries.
CVE-2007-2138
7.3, 7.4, 8.0, 8.1, 8.2 7.3.19, 7.4.17, 8.0.13, 8.1.9, 8.2.4 core server
Legacy: C
A vulnerability involving insecure search_path settings allows unprivileged users to gain the SQL privileges of the owner of any SECURITY DEFINER function they are allowed to call. Securing such a function requires both a software update and changes to the function definition.
CVE-2007-0556
8.0, 8.1, 8.2 8.0.11, 8.1.7, 8.2.2 core server
Legacy: C
A vulnerability involving changing the data type of a table column can easily be exploited to cause a backend crash, and in principle might be used to read database content that the user should not be able to access.
CVE-2007-0555
7.3, 7.4, 8.0, 8.1, 8.2 7.3.13, 7.4.16, 8.0.11, 8.1.7, 8.2.2 core server
Legacy: C
A vulnerability allows suppressing the normal checks that a SQL function returns the data type it's declared to do. These errors can easily be exploited to cause a backend crash, and in principle might be used to read database content that the user should not be able to access.

Unsupported versions

You can also view archived security patches for unsupported versions. Note that no further security patches are made available for these versions as they are end of life.
9.2 - 9.1 - 9.0 - 8.4 - 8.3 - 8.2 - 8.1 - 8.0 - 7.4 - 7.3

Components

The following component references are used in the above table:

Component Description
core server This vulnerability exists in the core server product.
client This vulnerability exists in a client library or client application only.
contrib module This vulnerability exists in a contrib module. Contrib modules are not installed by default when PostgreSQL is installed from source. They may be installed by binary packages.
client contrib module This vulnerability exists in a contrib module used on the client only.
packaging This vulnerability exists in PostgreSQL binary packaging, e.g. an installer or RPM.

Privacy Policy | About PostgreSQL | Twitter
Copyright © 1996-2018 The PostgreSQL Global Development Group