VuXML ID | Description |
2ccd71bd-426b-11ec-87db-6cc21735f730 | PostgreSQL -- Possible man-in-the-middle attacks
The PostgreSQL Project reports:
CVE-2021-23214: A man-in-the-middle with the ability to inject data into the TCP connection could stuff some cleartext data into the start of a supposedly encryption-protected database session. This could be abused to send faked SQL commands to the server, although that would only work if the server did not demand any authentication data. (However, a server relying on SSL certificate authentication might well not do so.)
CVE-2021-23222: A man-in-the-middle with the ability to inject data into the TCP connection could stuff some cleartext data into the start of a supposedly encryption-protected database session. This could probably be abused to inject faked responses to the client's first few queries, although other details of libpq's behavior make that harder than it sounds. A different line of attack is to exfiltrate the client's password, or other sensitive data that might be sent early in the session. That has been shown to be possible with a server vulnerable to CVE-2021-23214.
Discovery 2021-11-08 Entry 2021-11-10 postgresql14-server
< 14.1
postgresql13-server
< 13.5
postgresql12-server
< 12.9
postgresql11-server
< 11.14
postgresql10-server
< 10.19
postgresql96-server
< 9.6.24
CVE-2021-23214
CVE-2021-23222
|
157ce083-d145-11ec-ab9b-6cc21735f730 | PostgreSQL Server -- execute arbitrary SQL code as DBA user
The PostgreSQL project reports:
Confine additional operations within "security restricted
operation" sandboxes.
Autovacuum, CLUSTER, CREATE INDEX, REINDEX, REFRESH MATERIALIZED VIEW,
and pg_amcheck activated the "security restricted operation" protection
mechanism too late, or even not at all in some code paths.
A user having permission to create non-temporary objects within a
database could define an object that would execute arbitrary SQL
code with superuser permissions the next time that autovacuum
processed the object, or that some superuser ran one of the affected
commands against it.
Discovery 2022-05-11 Entry 2022-05-11 postgresql14-server
< 14.3
postgresql13-server
< 13.7
postgresql12-server
< 12.11
postgresql11-server
< 11.16
postgresql10-server
< 10.21
CVE-2022-1552
|
d331f691-71f4-11ea-8bb5-6cc21735f730 | PostgresSQL -- ALTER ... DEPENDS ON EXTENSION is missing authorization checks
The PostgreSQL project reports:
Versions Affected: 9.6 - 12
The ALTER ... DEPENDS ON EXTENSION sub-commands do not perform
authorization checks, which can allow an unprivileged user to drop
any function, procedure, materialized view, index, or trigger under
certain conditions. This attack is possible if an administrator has
installed an extension and an unprivileged user can CREATE, or an
extension owner either executes DROP EXTENSION predictably or can be
convinced to execute DROP EXTENSION.
Discovery 2020-02-13 Entry 2020-03-29 postgresql12-server
< 12.2
postgresql11-server
< 11.7
postgresql10-server
< 10.12
postgresql96-server
< 9.6.17
https://www.postgresql.org/about/news/1960/
CVE-2020-1720
|
62da9702-b4cc-11eb-b9c9-6cc21735f730 | PostgreSQL server -- two security issues
The PostgreSQL project reports:
Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE
Using an INSERT ... ON CONFLICT ... DO UPDATE command on a
purpose-crafted table, an attacker can read arbitrary bytes of
server memory. In the default configuration, any authenticated
database user can create prerequisite objects and complete this
attack at will. A user lacking the CREATE and TEMPORARY privileges
on all databases and the CREATE privilege on all schemas cannot use
this attack at will..
Buffer overrun from integer overflow in array subscripting
calculations
While modifying certain SQL array values, missing bounds checks let
authenticated database users write arbitrary bytes to a wide area of
server memory.
Discovery 2021-05-13 Entry 2021-05-14 postgresql13-server
< 13.3
postgresql12-server
< 12.7
postgresql11-server
< 11.12
postgresql10-server
< 10.17
postgresql96-server
< 9.6.22
https://www.postgresql.org/support/security/CVE-2021-32027/
https://www.postgresql.org/support/security/CVE-2021-32028/
|