Bitnami package
postgresql
pkg:bitnami/postgresql
Vulnerabilities (86)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-5869 | Hig | 8.8 | >= 11.0.0, < 11.22.0 | 11.22.0 | Dec 10, 2023 | A flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overfl | |
| CVE-2023-5868 | Med | 4.3 | >= 11.0.0, < 11.22.0 | 11.22.0 | Dec 10, 2023 | A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclo | |
| CVE-2020-21469 | Med | 4.4 | >= 12.2.0, < 12.2.1 | 12.2.1 | Aug 22, 2023 | An issue was discovered in PostgreSQL 12.2 allows attackers to cause a denial of service via repeatedly sending SIGHUP signals. NOTE: this is disputed by the vendor because untrusted users cannot send SIGHUP signals; they can only be sent by a PostgreSQL superuser, a user with pg | |
| CVE-2023-39418 | Low | 3.1 | >= 15.0.0, < 15.4.0 | 15.4.0 | Aug 11, 2023 | A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defined for UPDATE and SELECT. If UPDATE and SELECT policies forbid some rows that INSERT policies do not forbid, a user could store such rows. | |
| CVE-2023-39417 | Hig | 7.5 | >= 11.0.0, < 11.21.0 | 11.21.0 | Aug 11, 2023 | IN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, '', or ""). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, a | |
| CVE-2023-2455 | Med | 5.4 | >= 11.0.0, < 11.20.0 | 11.20.0 | Jun 9, 2023 | Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happe | |
| CVE-2023-2454 | Hig | 7.2 | >= 11.0.0, < 11.20.0 | 11.20.0 | Jun 9, 2023 | schema_element defeats protective search_path changes; It was found that certain database calls in PostgreSQL could permit an authed attacker with elevated database-level privileges to execute arbitrary code. | |
| CVE-2022-41862 | Low | 3.7 | >= 12.0.0, < 12.14.0 | 12.14.0 | Mar 3, 2023 | In PostgreSQL, a modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. In certain conditions a server can cause a libpq client to over-read and report an error message containing uninitialized bytes. | |
| CVE-2022-1552 | Hig | 8.8 | >= 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 | Med | 5.9 | >= 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 | Hig | 8.0 | >= 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 | Hig | 8.1 | < 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 | Med | 6.5 | >= 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 | Med | 5.9 | >= 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 | Med | 6.5 | >= 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 | Med | 6.5 | >= 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 | Hig | 8.8 | >= 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 | Med | 4.3 | < 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 | Med | 4.3 | >= 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 | Hig | 7.5 | >= 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 |
- affected >= 11.0.0, < 11.22.0fixed 11.22.0
A flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overfl
- affected >= 11.0.0, < 11.22.0fixed 11.22.0
A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclo
- affected >= 12.2.0, < 12.2.1fixed 12.2.1
An issue was discovered in PostgreSQL 12.2 allows attackers to cause a denial of service via repeatedly sending SIGHUP signals. NOTE: this is disputed by the vendor because untrusted users cannot send SIGHUP signals; they can only be sent by a PostgreSQL superuser, a user with pg
- affected >= 15.0.0, < 15.4.0fixed 15.4.0
A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defined for UPDATE and SELECT. If UPDATE and SELECT policies forbid some rows that INSERT policies do not forbid, a user could store such rows.
- affected >= 11.0.0, < 11.21.0fixed 11.21.0
IN THE EXTENSION SCRIPT, a SQL Injection vulnerability was found in PostgreSQL if it uses @extowner@, @extschema@, or @extschema:...@ inside a quoting construct (dollar quoting, '', or ""). If an administrator has installed files of a vulnerable, trusted, non-bundled extension, a
- affected >= 11.0.0, < 11.20.0fixed 11.20.0
Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happe
- affected >= 11.0.0, < 11.20.0fixed 11.20.0
schema_element defeats protective search_path changes; It was found that certain database calls in PostgreSQL could permit an authed attacker with elevated database-level privileges to execute arbitrary code.
- affected >= 12.0.0, < 12.14.0fixed 12.14.0
In PostgreSQL, a modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. In certain conditions a server can cause a libpq client to over-read and report an error message containing uninitialized bytes.
- affected >= 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
- affected >= 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
- affected >= 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
- affected < 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
- affected >= 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
- affected >= 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.
- affected >= 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.
- affected >= 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.
- affected >= 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
- affected < 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
- affected >= 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.
- affected >= 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
Page 4 of 5