Bitnami package
postgresql
pkg:bitnami/postgresql
Vulnerabilities (58)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-1552 | — | >= 10.0.0, < 10.21.0 | 10.21.0 | Aug 31, 2022 | 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 protecti | ||
| CVE-2021-43767 | — | >= 9.6.0, < 9.6.24 | 9.6.24 | Aug 25, 2022 | Odyssey passes to client unencrypted bytes from man-in-the-middle When Odyssey storage is configured to use the PostgreSQL server using 'trust' authentication with a 'clientcert' requirement or to use 'cert' authentication, a man-in-the-middle attacker can inject false responses | ||
| CVE-2022-2625 | — | >= 10.0.0, < 10.22.0 | 10.22.0 | Aug 18, 2022 | 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 | ||
| CVE-2021-23214 | — | < 9.6.24 | 9.6.24 | Mar 4, 2022 | 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 encrypt | ||
| CVE-2021-3677 | — | >= 11.0.0, < 11.13.0 | 11.13.0 | Mar 2, 2022 | 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 | ||
| CVE-2021-23222 | — | >= 9.6.0, < 9.6.24 | 9.6.24 | Mar 2, 2022 | 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. | ||
| CVE-2021-32028 | — | >= 9.6.0, < 9.6.22 | 9.6.22 | Oct 11, 2021 | 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. | ||
| CVE-2021-32029 | — | >= 11.0.0, < 11.12.0 | 11.12.0 | Oct 8, 2021 | 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. | ||
| CVE-2021-32027 | — | >= 9.6.0, < 9.6.22 | 9.6.22 | Jun 1, 2021 | A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory. The highest t | ||
| CVE-2021-3393 | — | < 11.11.0 | 11.11.0 | Apr 1, 2021 | An information leak was discovered in postgresql in versions before 13.2, before 12.6 and before 11.11. A user having UPDATE permission but not SELECT permission to a particular column could craft queries which, under some circumstances, might disclose values from that column in | ||
| CVE-2021-20229 | — | >= 13.0.0, < 13.2.0 | 13.2.0 | Feb 23, 2021 | A flaw was found in PostgreSQL in versions before 13.2. This flaw allows a user with SELECT privilege on one column to craft a special query that returns all columns of the table. The highest threat from this vulnerability is to confidentiality. | ||
| CVE-2020-25696 | — | >= 9.5.0, < 9.5.24 | 9.5.24 | Nov 23, 2020 | A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code | ||
| CVE-2020-25695 | — | < 9.5.24 | 9.5.24 | Nov 16, 2020 | A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuse | ||
| CVE-2020-25694 | — | < 9.5.24 | 9.5.24 | Nov 16, 2020 | A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant paramet | ||
| CVE-2020-10733 | — | >= 9.5.0, < 9.5.22 | 9.5.22 | Sep 16, 2020 | The Windows installer for PostgreSQL 9.5 - 12 invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having perm | ||
| CVE-2020-14350 | — | >= 9.5.0, < 9.5.23 | 9.5.23 | Aug 24, 2020 | It was found that some PostgreSQL extensions did not use search_path safely in their installation script. An attacker with sufficient privileges could use this flaw to trick an administrator into executing a specially crafted script, during the installation or update of such exte | ||
| CVE-2020-14349 | — | >= 10.0.0, < 10.14.0 | 10.14.0 | Aug 24, 2020 | It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize the search_path during logical replication. An authenticated attacker could use this flaw in an attack similar to CVE-2018-1058, in order to execute arbitrary SQL command in | ||
| CVE-2020-1720 | — | >= 9.6.0, < 9.6.17 | 9.6.17 | Mar 17, 2020 | A flaw was found in PostgreSQL's "ALTER ... DEPENDS ON EXTENSION", where sub-commands did not perform authorization checks. An authenticated attacker could use this flaw in certain configurations to perform drop objects such as function, triggers, et al., leading to database corr |
- CVE-2022-1552Aug 31, 2022affected >= 10.0.0, < 10.21.0fixed 10.21.0
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 protecti
- CVE-2021-43767Aug 25, 2022affected >= 9.6.0, < 9.6.24fixed 9.6.24
Odyssey passes to client unencrypted bytes from man-in-the-middle When Odyssey storage is configured to use the PostgreSQL server using 'trust' authentication with a 'clientcert' requirement or to use 'cert' authentication, a man-in-the-middle attacker can inject false responses
- CVE-2022-2625Aug 18, 2022affected >= 10.0.0, < 10.22.0fixed 10.22.0
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
- CVE-2021-23214Mar 4, 2022affected < 9.6.24fixed 9.6.24
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 encrypt
- CVE-2021-3677Mar 2, 2022affected >= 11.0.0, < 11.13.0fixed 11.13.0
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
- CVE-2021-23222Mar 2, 2022affected >= 9.6.0, < 9.6.24fixed 9.6.24
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.
- CVE-2021-32028Oct 11, 2021affected >= 9.6.0, < 9.6.22fixed 9.6.22
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.
- CVE-2021-32029Oct 8, 2021affected >= 11.0.0, < 11.12.0fixed 11.12.0
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.
- CVE-2021-32027Jun 1, 2021affected >= 9.6.0, < 9.6.22fixed 9.6.22
A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory. The highest t
- CVE-2021-3393Apr 1, 2021affected < 11.11.0fixed 11.11.0
An information leak was discovered in postgresql in versions before 13.2, before 12.6 and before 11.11. A user having UPDATE permission but not SELECT permission to a particular column could craft queries which, under some circumstances, might disclose values from that column in
- CVE-2021-20229Feb 23, 2021affected >= 13.0.0, < 13.2.0fixed 13.2.0
A flaw was found in PostgreSQL in versions before 13.2. This flaw allows a user with SELECT privilege on one column to craft a special query that returns all columns of the table. The highest threat from this vulnerability is to confidentiality.
- CVE-2020-25696Nov 23, 2020affected >= 9.5.0, < 9.5.24fixed 9.5.24
A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code
- CVE-2020-25695Nov 16, 2020affected < 9.5.24fixed 9.5.24
A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuse
- CVE-2020-25694Nov 16, 2020affected < 9.5.24fixed 9.5.24
A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant paramet
- CVE-2020-10733Sep 16, 2020affected >= 9.5.0, < 9.5.22fixed 9.5.22
The Windows installer for PostgreSQL 9.5 - 12 invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having perm
- CVE-2020-14350Aug 24, 2020affected >= 9.5.0, < 9.5.23fixed 9.5.23
It was found that some PostgreSQL extensions did not use search_path safely in their installation script. An attacker with sufficient privileges could use this flaw to trick an administrator into executing a specially crafted script, during the installation or update of such exte
- CVE-2020-14349Aug 24, 2020affected >= 10.0.0, < 10.14.0fixed 10.14.0
It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize the search_path during logical replication. An authenticated attacker could use this flaw in an attack similar to CVE-2018-1058, in order to execute arbitrary SQL command in
- CVE-2020-1720Mar 17, 2020affected >= 9.6.0, < 9.6.17fixed 9.6.17
A flaw was found in PostgreSQL's "ALTER ... DEPENDS ON EXTENSION", where sub-commands did not perform authorization checks. An authenticated attacker could use this flaw in certain configurations to perform drop objects such as function, triggers, et al., leading to database corr
Page 3 of 3