The PostgreSQL Global Development Group (PGDG) takes security seriously. This allows our users to place their trust in PostgreSQL for protecting their mission-critical data.
The PostgreSQL Global Development Group follows a model that shares responsibility between PostgreSQL itself and its deployment environment, including hardware, operating system, and the application layer (programming language, frameworks and client libraries). The PostgreSQL documentation provides info on the inherent security features of PostgreSQL and how to securely configure and run PostgreSQL.
Security vulnerabilities can exist both in PostgreSQL and software within the PostgreSQL ecosystem, including client libraries, extensions, installers, and other utilities. This page walks through what is considered a security vulnerability in PostgreSQL, how to report PostgreSQL security vulnerabilities, and how fixes for security vulnerabilities are released.
Please note that the PostgreSQL Project does not offer bug bounties.
The PostgreSQL Project is a CVE Numbering Authority (CNA), working with Red Hat as our CNA Root. This allows us to assign our own CVE numbers and publish CVE records for PostgreSQL and closely related projects.
We will currently assign CVE numbers for the following projects upon request to [email protected]:
Additional projects may request inclusion on the list above by emailing [email protected].
NOTE: The security team will only assign CVEs to projects when requested by members of the project. If you think you've found a security issue in a project other than PostgreSQL or it's packages and installers, please contact the security team for that project. See below for more details.
A security vulnerability in PostgreSQL is an issue that allows a user to gain access to privileges or data that they do not have permission to use, or allows a user to execute arbitrary code through a PostgreSQL process.
The PostgreSQL Security Team does not consider reports on actions a PostgreSQL superuser takes to be a security vulnerability. However, a report on an unprivileged user escalating to superuser generally qualifies as valid.
The PostgreSQL Security Team typically does not consider a denial-of-service on a PostgreSQL server from an authenticated, valid SQL statement to be a security vulnerability. A denial-of-service issue of this nature could still be a bug, and we encourage you to report it on the Report a Bug page.
Please do not report the lack of DMARC on postgresql.org mailing lists. This is by design.
For security vulnerabilities in PostgreSQL or any of the installers linked from the PostgreSQL download page, please email [email protected].
For reporting non-security bugs, please visit the Report a Bug page.
If you are unsure if an issue is a security vulnerability, please err on the side of caution and email [email protected].
Please see below for how you can report security vulnerabilities in PostgreSQL-related projects:
The PostgreSQL Project releases security fixes as part of minor version updates. You are always advised to use the latest minor version available, as it will contain other non-security related fixes.
A new PostgreSQL major release, which contains new features, has every prior security fix.
If you find a security vulnerability in PostgreSQL, the PostgreSQL Security Team will credit you in the release notes and register a CVE for the vulnerability. Please do not register a CVE independently of the PostgreSQL Security Team.
To receive notifications about security releases or other security related news, you can subscribe to the pgsql-announce mailing list. If you set your subscription to only include the tag Security, it will exclude all other announcements that are sent to this list.
The PostgreSQL Global Development Group 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 security vulnerabilities over a range of criteria. This includes:
You can find more detailed information about a security vulnerability by clicking on the links in the table below.
You are currently viewing PostgreSQL security vulnerabilities for an unsupported version. If you are still using PostgreSQL 8.3, you should upgrade as soon as possible.
You can filter the view of patches to show just patches for version:
17 -
16 -
15 -
14 -
13
- all
| Reference | Affected | Fixed | Component & CVSS v3 Base Score | Description |
|---|---|---|---|---|
|
CVE-2013-0255 |
9.2, 9.1, 9.0, 8.4, 8.3 | 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23 | core server Legacy: D |
executing enum_recv() with wrong parameters crashes server more details |
|
CVE-2012-3489 |
9.1, 9.0, 8.4, 8.3 | 9.1.5, 9.0.9, 8.4.13, 8.3.20 | core server Legacy: C |
xml_parse() DTD validation can be used to read arbitrary files more details |
|
CVE-2012-3488 |
9.1, 9.0, 8.4, 8.3 | 9.1.5, 9.0.9, 8.4.13, 8.3.20 | contrib module Legacy: C |
contrib/xml2's xslt_process() can be used to read and write arbitrary files more details |
|
CVE-2012-2655 |
9.1, 9.0, 8.4, 8.3 | 9.1.4, 9.0.8, 8.4.12, 8.3.19 | core server Legacy: D |
SECURITY DEFINER and SET attributes on procedural call handlers are not ignored and can be used to crash the server more details |
|
CVE-2012-2143 |
9.1, 9.0, 8.4, 8.3 | 9.1.4, 9.0.8, 8.4.12, 8.3.19 | contrib module Legacy: C |
Passwords containing the byte 0x80 passed to the crypt() function in pgcrypto are incorrectly truncated if DES encryption was used more details |
|
CVE-2012-0868 |
9.1, 9.0, 8.4, 8.3 | 9.1.3, 9.0.7, 8.4.11, 8.3.18 | core server Legacy: C |
Line breaks in object names can be exploited to execute arbitrary SQL when reloading a pg_dump file. more details |
|
CVE-2012-0866 |
9.1, 9.0, 8.4, 8.3 | 9.1.3, 9.0.7, 8.4.11, 8.3.18 | core server Legacy: C |
Permissions on a function called by a trigger are not properly checked. more details |
|
CVE-2010-4015 |
9.0, 8.4, 8.3, 8.2 | 9.0.3, 8.4.7, 8.3.14, 8.2.20 | contrib module Legacy: C |
An authenticated database user can cause a buffer overrun by calling functions from the intarray optional module with certain parameters. more details |
|
CVE-2010-3433 |
9.0, 8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 9.0.1, 8.4.5, 8.3.12, 8.2.18, 8.1.22, 8.0.26, 7.4.30 | 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 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29 | 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. more details |
|
CVE-2010-1170 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29 | 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. more details |
|
CVE-2010-1169 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29 | 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. more details |
|
CVE-2009-4136 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.2, 8.3.9, 8.2.15, 8.1.19, 8.0.23, 7.4.27 | 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). more details |
|
CVE-2009-4034 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.2, 8.3.9, 8.2.15, 8.1.19, 8.0.23, 7.4.27 | 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. more details |
|
CVE-2009-3231 |
8.3, 8.2 | 8.3.8, 8.2.14 | 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. more details |
|
CVE-2009-3230 |
8.4, 8.3, 8.2, 8.1, 8.0, 7.4 | 8.4.1, 8.3.8, 8.2.14, 8.1.18, 8.0.22, 7.4.26 | core server Legacy: C |
The fix for issue CVE-2007-6600 (below) failed to include protection against misuse of RESET SESSION AUTHORIZATION. more details |
|
CVE-2009-3229 |
8.4, 8.3, 8.2 | 8.4.1, 8.3.8, 8.2.14 | 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. more details |
|
CVE-2009-0922 |
8.3, 8.2, 8.1, 8.0, 7.4 | 8.3.7, 8.2.13, 8.1.17, 8.0.21, 7.4.25 | 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. more details |
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.
12 -
11 -
10 -
9.6 -
9.5 -
9.4 -
9.3 -
9.2 -
9.1 -
9.0 -
8.4 -
8.3 -
8.2 -
8.1 -
8.0 -
7.4 -
7.3
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. |
The PostgreSQL Security Team is made up of a group of contributors to the PostgreSQL project who have experience in different aspects of database and information security.
You can find a list of members on the security team here: