rpm package
opensuse/postgresql11&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/postgresql11&distro=openSUSE%20Tumbleweed
Vulnerabilities (28)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-5870 | — | < 11.22-1.1 | 11.22-1.1 | Dec 10, 2023 | A flaw was found in PostgreSQL involving the pg_cancel_backend role that signals background workers, including the logical replication launcher, autovacuum workers, and the autovacuum launcher. Successful exploitation requires a non-core extension with a less-resilient background | ||
| CVE-2023-5868 | — | < 11.22-1.1 | 11.22-1.1 | 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-2023-5869 | — | < 11.22-1.1 | 11.22-1.1 | 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-39417 | — | < 11.21-1.1 | 11.21-1.1 | 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 | — | < 11.20-1.1 | 11.20-1.1 | 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 | — | < 11.20-1.1 | 11.20-1.1 | 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-1552 | — | < 11.16-1.1 | 11.16-1.1 | 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-2022-2625 | — | < 11.17-1.1 | 11.17-1.1 | 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 | — | < 11.14-1.1 | 11.14-1.1 | 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.13-1.3 | 11.13-1.3 | 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 | — | < 11.14-1.1 | 11.14-1.1 | 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 | — | < 11.13-1.3 | 11.13-1.3 | 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.13-1.3 | 11.13-1.3 | 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 | — | < 11.13-1.3 | 11.13-1.3 | 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.13-1.3 | 11.13-1.3 | 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-2020-25696 | — | < 11.13-1.3 | 11.13-1.3 | 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 | — | < 11.13-1.3 | 11.13-1.3 | 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 | — | < 11.13-1.3 | 11.13-1.3 | 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-14350 | — | < 11.13-1.3 | 11.13-1.3 | 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 | — | < 11.13-1.3 | 11.13-1.3 | 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-2023-5870Dec 10, 2023affected < 11.22-1.1fixed 11.22-1.1
A flaw was found in PostgreSQL involving the pg_cancel_backend role that signals background workers, including the logical replication launcher, autovacuum workers, and the autovacuum launcher. Successful exploitation requires a non-core extension with a less-resilient background
- CVE-2023-5868Dec 10, 2023affected < 11.22-1.1fixed 11.22-1.1
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-2023-5869Dec 10, 2023affected < 11.22-1.1fixed 11.22-1.1
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-39417Aug 11, 2023affected < 11.21-1.1fixed 11.21-1.1
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-2455Jun 9, 2023affected < 11.20-1.1fixed 11.20-1.1
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-2454Jun 9, 2023affected < 11.20-1.1fixed 11.20-1.1
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-1552Aug 31, 2022affected < 11.16-1.1fixed 11.16-1.1
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-2022-2625Aug 18, 2022affected < 11.17-1.1fixed 11.17-1.1
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 < 11.14-1.1fixed 11.14-1.1
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.13-1.3fixed 11.13-1.3
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 < 11.14-1.1fixed 11.14-1.1
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 < 11.13-1.3fixed 11.13-1.3
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.13-1.3fixed 11.13-1.3
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 < 11.13-1.3fixed 11.13-1.3
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.13-1.3fixed 11.13-1.3
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-2020-25696Nov 23, 2020affected < 11.13-1.3fixed 11.13-1.3
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 < 11.13-1.3fixed 11.13-1.3
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 < 11.13-1.3fixed 11.13-1.3
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-14350Aug 24, 2020affected < 11.13-1.3fixed 11.13-1.3
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 < 11.13-1.3fixed 11.13-1.3
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
Page 1 of 2