postgresql-13 - security update
postgresql-13 - security update
- Update to 13.23-0+deb11u1
Published Updated
PatchFirst · Latest vulnerabilities
postgresql-13 vulnerabilities
Vulnerabilities published for postgresql-13 in the last 30 days: 0. Listed in the KEV catalogue: 0.
Vulnerabilities: 26
postgresql-13 - security update
postgresql-13 - security update
- Update to 13.22-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.21-0+deb11u1
Published Updatedpostgresql-13 - regression update
postgresql-13 - regression update
- Update to 13.20-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.19-0+deb11u1
Published Updatedpostgresql-13 - regression update
postgresql-13 - regression update
- Update to 13.18-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.17-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.16-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.14-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.13-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.11-0+deb11u1
Published UpdatedCVE-2022-1552
A flaw was found in PostgreSQL. There is an issue with incomplete efforts to operate safely when a privileged user is maintaining another user's objects. The Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck commands activated relevant protections too late or not at all during the process. This flaw allows an attacker with permission to create non-temporary objects in at least one schema to execute arbitrary SQL functions under a superuser identity.
- Update to 13.7-0+deb11u1
Published UpdatedCVE-2022-2625
A vulnerability was found in PostgreSQL. This attack requires permission to create non-temporary objects in at least one schema, the ability to lure or wait for an administrator to create or update an affected extension in that schema, and the ability to lure or wait for a victim to use the object targeted in CREATE OR REPLACE or CREATE IF NOT EXISTS. Given all three prerequisites, this flaw allows an attacker to run arbitrary code as the victim role, which may be a superuser.
- Update to 13.8-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.7-0+deb11u1
Published UpdatedCVE-2021-23214
When the server is configured to use trust authentication with a clientcert requirement or to use cert authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of SSL certificate verification and encryption.
- Update to 13.5-0+deb11u1
Published UpdatedCVE-2021-3677
A flaw was found in postgresql. A purpose-crafted query can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can complete this attack at will. The attack does not require the ability to create objects. If server settings include max_worker_processes=0, the known versions of this attack are infeasible. However, undiscovered variants of the attack may be independent of that setting.
- Update to 13.4-0+deb11u1
Published UpdatedCVE-2021-23222
A man-in-the-middle attacker can inject false responses to the client's first few queries, despite the use of SSL certificate verification and encryption.
- Update to 13.5-0+deb11u1
Published Updatedpostgresql-13 - security update
postgresql-13 - security update
- Update to 13.5-0+deb11u1
Published UpdatedCVE-2021-32028
A flaw was found in postgresql. Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an authenticated database user could read arbitrary bytes of server memory. The highest threat from this vulnerability is to data confidentiality.
- Update to 13.3-1
Published UpdatedCVE-2021-32029
A flaw was found in postgresql. Using an UPDATE ... RETURNING command on a purpose-crafted table, an authenticated database user could read arbitrary bytes of server memory. The highest threat from this vulnerability is to data confidentiality.
- Update to 13.3-1
Published Updated
Check your server
Check your installed stack and versions against the current vulnerability feeds.