PostgreSQL 14

对于希望从任何以前的版本迁移数据的人来说，需要使用pg_dumpall进行转储/恢复，或者使用pg_upgrade或逻辑复制。有关迁移到新主要版本的通用信息，请参阅第 19.6 节。

版本 14 包含许多可能影响与先前版本兼容性的变更。请注意以下不兼容性：

Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a "refint" cascade primary key and facilitates user-controlled updates to that column. In that case, a SQL injection allows a primary key update value provider to execute arbitrary SQL as the database user performing the primary key update. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：避免 contrib/refint 的 check_foreign_key() 中解引用 NULL 指针
• 14.23：防止 contrib/spi 中的 SQL 注入和缓冲区越界写

Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

发布说明中的提及：

• 14.23：防止处理启动包时发生无界递归

Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.23：在认证代码中使用时序安全的字符串比较

Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：client。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.23：将 PQfn() 标记为不安全，并避免在 libpq 内部使用它

Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：client。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.23：防止 pg_basebackup 和 pg_rewind 中的路径遍历

Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server memory, via crafted timezone zones. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.23：防范 timeofday() 和 pg_strftime() 中的恶意时区名

Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 PL/Perl 和 PL/Tcl 内存分配计算中的整数溢出
• 14.23：修复内存分配计算中的多处整数溢出问题
• 14.23：拒绝 ts_headline() 中过长的选项
• 14.23：防范 contrib/intarray 的 query_int 类型以及 contrib/ltree 的 ltxtquery 类型中的字段溢出
• 14.23：防范 contrib/ltree 的 lquery 类型中过长的值

Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.23。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.23：创建多范围类型时，确保用户在为该多范围类型指定的模式上拥有 CREATE 权限

Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：将逻辑解码输出插件限制为新服务器参数 output_plugin_libraries 指定的集合

Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

发布说明中的提及：

• 14.24：在此前漏检的场景中检查数据类型的 USAGE 权限

Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves nothing in many ownership arrangements. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L

发布说明中的提及：

• 14.24：在 ALTER TABLE 重建扩展统计信息对象时保留其所有权

Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：client。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 psql：跳过脚本中的 COPY ... FROM STDIN 命令后面的内联数据，即使 COPY 在发送 PGRES_COPY_IN 前失败

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.21。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.22：避免在对“经过 TOAST 处理”的数据应用 substring() 时误报无效编码
• 14.21：修复多字节字符长度验证不充分的问题

Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.21。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.21：修复 contrib/pgcrypto PGP 解密函数中的缓冲区溢出问题

Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.21。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.21：增强选择率估算器在被附加到接受非预期数据类型的操作符时的防护

Improper validation of type "oidvector" in PostgreSQL allows a database user to disclose a few bytes of server memory. We have not ruled out viability of attacks that arrange for presence of confidential information in disclosed bytes, but they seem unlikely. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.21。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.21：防止 oidvector/int2vector 出现意外的维度

Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：client。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：移除 pg_dump 关于 pg_proc.protrftypes 不可能包含超过 FUNC_MAX_ARGS 个条目的假设

Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：client。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：不要对 psql 的 \unrestrict 命令参数执行反引号扩展

Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end of a specific allocation, via a crafted text value. This is the same class of defect that CVE-2026-2006 fixed, though this instance has less impact. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.24：增强 ascii() 函数对无效输入的防护

Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix. The client overwrites a huge memory region with bytes outside attacker knowledge or control. This typically yields a simple SIGSEGV, but rare cases might achieve client-specific integrity impact via the write. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：client。

官方受影响分支记录：14。

AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L

发布说明中的提及：

• 14.24：修复 ecpg 应用程序因接收服务器返回的无效 bytea 数据而发生的越界写入

Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：交叉检查运行 EXECUTE 或 FETCH 的 portal 的输出行类型

Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary code as the operating system user running the database, via conflation of range and multirange values. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.

以上保留官方英文漏洞说明。

尚未记录本分支的修复版本。组件：core server。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 pg_restore_attribute_stats() 对多范围类型的处理

Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 contrib/fuzzystrmatch 的 levenshtein() 和 levenshtein_less_equal() 函数中的整数溢出

SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：逆解析 EXTRACT() 函数调用时，按需为字段名加引号

Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.6 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.

以上保留官方英文漏洞说明。

尚未记录本分支的修复版本。组件：core server。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.24：在直接 SSL 连接之后拒绝 GSSEncRequest

Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：拒绝从 SQL 调用接受或返回 internal 类型的函数

Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

发布说明中的提及：

• 14.24：修复多处错误地假定无需处理超过 FUNC_MAX_ARGS 个函数参数的问题

Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer. This might allow a table maintainer to infer limited memory values, via the lossy signal of index split choices. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.24：修复 contrib/pg_trgm 的 GiST picksplit 函数中的数据类型错误

Integer wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies. This may execute arbitrary code as the operating system user running the database. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 PL/Perl 和 PL/Tcl 内存分配计算中的整数溢出

Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.

以上保留官方英文漏洞说明。

尚未记录本分支的修复版本。组件：contrib module。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 contrib/pg_stat_statements 中的缓冲区越界写入

Untrusted search path in PostgreSQL amcheck allows a grantee of amcheck function EXECUTE privilege to execute arbitrary functions as the owners of expression indexes that depend on the search path, via setting a hostile search path before calling the amcheck function. Within major versions 18, 16, 15, and 14, minor versions before PostgreSQL 18.6, 16.15, 15.19, and 14.24 are affected. PostgreSQL 17 is unaffected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.24：确保 contrib/amcheck 函数在执行索引表达式前限制 search_path

Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test the existence of a user via observing the SCRAM iteration count. This requires the probed user to have a non-default scram_iterations count, because the authentication challenge for a nonexistent user reports the default scram_iterations. Within major versions 16-18, minor versions before PostgreSQL 18.6, 17.11, and 16.15 are affected. Versions before PostgreSQL 16 are unaffected.

以上保留官方英文漏洞说明。

尚未记录本分支的修复版本。组件：core server。

AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.24：让模拟的 SCRAM secret 更可信

Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：移除 contrib/refint 中的计划缓存

Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：增强 PL/Perl 对“tied” Perl 数组和 hash 的防护

Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复 to_char() 处理过长时区缩写时发生的缓冲区越界写入

Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

发布说明中的提及：

• 14.24：让 scalarineqsel() 检查预期为 tid 类型的常量是否确实属于该类型

Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies continue until some other event invalidates the cache or connection termination ends the session. This permits a user to complete reads and modifications that were recently permitted but now forbidden. An attacker must tailor an attack to a particular application's pattern of privilege removal and role-specific row security policies. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.24：角色发生变更后使依赖角色的缓存计划失效

Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the operating system user running the database, via text that would not pass encoding validation. This shares heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through pg_wchar. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：修复正则表达式匹配/拆分函数中的缓冲区越界写入

Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed even with the wrong key. This in turn loses the modest protection from the Modification Detection Code (MDC). Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：contrib module。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.24：修复 contrib/pgcrypto 的 PGP 加密，使其能够检测不受支持的密码算法

Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs. This may execute arbitrary code as the operating system user running the database. These types are typically sourced from application logic, not taken from the application's user. Hence, application users attacking the database, through the application as a conduit, are unlikely. CVE-2026-6473 had fixed similar problems. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.24。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：增强 tsvector 和 tsquery 代码对超长值的防护（包括单个词位以及向量/查询的总长度）

Improper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.

以上保留官方英文漏洞说明。

本分支修复于：14.19。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.19：在 pg_dump 输出的注释中，将名称中包含的换行符转换为空格

Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. This is similar to MySQL CVE-2024-21096. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.19。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.24：不要对 psql 的 \unrestrict 命令参数执行反引号扩展
• 14.19：防止 pg_dump 脚本被用于攻击执行恢复的用户

PostgreSQL optimizer statistics allow a user to read sampled data within a view that the user cannot access. Separately, statistics allow a user to read sampled data that a row security policy intended to hide. PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user could craft a leaky operator that bypassed view access control lists (ACLs) and bypassed row security policies in partitioning or table inheritance hierarchies. Reachable statistics data notably included histograms and most-common-values lists. CVE-2017-7484 and CVE-2019-10130 intended to close this class of vulnerability, but this gap remained. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.19。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.19：加强规划器估算函数中的安全检查

Buffer over-read in PostgreSQL GB18030 encoding validation allows a database input provider to achieve temporary denial of service on platforms where a 1-byte over-read can elicit process termination. This affects the database server and also libpq. Versions before PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.18。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

发布说明中的提及：

• 14.18：避免在检查声称为 GB18030 编码的无效编码字符串时发生单字节缓冲区越界读取

Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write out-of-bounds by hundreds of megabytes. This results in a segmentation fault for the application using libpq. Versions before PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.20。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

发布说明中的提及：

• 14.20：避免 libpq 中分配大小计算的整数溢出

Missing authorization in PostgreSQL CREATE STATISTICS command allows a table owner to achieve denial of service against other CREATE STATISTICS users by creating in any schema. A later CREATE STATISTICS for the same name, from a user having the CREATE privilege, would then fail. Versions before PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.20。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

发布说明中的提及：

• 14.20：检查 CREATE STATISTICS 中模式的 CREATE 权限

Improper neutralization of quoting syntax in PostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() allows a database input provider to achieve SQL injection in certain usage patterns. Specifically, SQL injection requires the application to use the function result to construct input to psql, the PostgreSQL interactive terminal. Similarly, improper neutralization of quoting syntax in PostgreSQL command line utility programs allows a source of command line arguments to achieve SQL injection when client_encoding is BIG5 and server_encoding is one of EUC_TW or MULE_INTERNAL. Versions before PostgreSQL 17.3, 16.7, 15.11, 14.16, and 13.19 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.16。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.17：改进 libpq 引用函数的行为
• 14.16：加强 PQescapeString 及相关函数对无效编码输入字符串的防护

Time-of-check Time-of-use (TOCTOU) race condition in pg_dump in PostgreSQL allows an object creator to execute arbitrary SQL functions as the user running pg_dump, which is often a superuser. The attack involves replacing another relation type with a view or foreign table. The attack requires waiting for pg_dump to start, but winning the race condition is trivial if the attacker retains an open transaction. Versions before PostgreSQL 16.4, 15.8, 14.13, 13.16, and 12.20 are affected. The PostgreSQL project thanks Noah Misch for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.13。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.13：防止在 pg_dump 期间执行未经授权的代码

Missing authorization in PostgreSQL built-in views pg_stats_ext and pg_stats_ext_exprs allows an unprivileged database user to read most common values and other statistics from CREATE STATISTICS commands of other users. The most common values may reveal column values the eavesdropper could not otherwise read or results of functions they cannot execute. Installing an unaffected version only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after installing that version. Current PostgreSQL installations will remain vulnerable until they follow the instructions in the release notes, which are provided as a convenience in the below section. Within major versions 14-16, minor versions before PostgreSQL 16.3, 15.7, and 14.12 are affected. Versions before PostgreSQL 14 are unaffected. This fix only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after this fix is applied. If you have a current PostgreSQL installation and are concerned about this issue, please use the following remediation steps to fix the issue: From the above URLs, you can click the URL that says "raw" to download a version that you can copy and paste. Be sure to use the script appropriate to your PostgreSQL major version. If you do not see this file, either your version is not vulnerable (only PostgreSQL 14, 15, and 16 are affected) or your minor version is too old to have the fix. \i /usr/share/postgresql/fix-CVE-2024-4317.sql ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true; After executing the fix-CVE-2024-4317.sql script in template0 and template1 , you should revoke the ability for template0 to accept connections. You can do this with the following command: ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false; The PostgreSQL project thanks Lukas Fittl for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.12。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.12：将 pg_stats_ext 和 pg_stats_ext_exprs 条目的可见性限制为表所有者

Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH ). That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. The PostgreSQL project thanks Coby Abrams for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.14。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.14：防止受信任的 PL/Perl 代码更改环境变量

Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE , SET SESSION AUTHORIZATION , or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION . The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. The PostgreSQL project thanks Tom Lane for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.14。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.15：恢复 ALTER {ROLE|DATABASE} SET role 的功能
• 14.14：修复 SET SESSION AUTHORIZATION 与 SET ROLE 之间意外的交互

Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results. This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. The PostgreSQL project thanks Jacob Champion for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.14。组件：client。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

发布说明中的提及：

• 14.14：使 libpq 丢弃在 SSL 或 GSS 协议协商期间收到的错误消息

Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes. They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy. This has the same consequences as the two earlier CVEs. That is to say, it leads to potentially incorrect policies being applied in 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 happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

以上保留官方英文漏洞说明。

本分支修复于：14.14。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.14：确保当 RLS 应用于非顶级表引用时，缓存的执行计划被标记为依赖于调用角色

UPDATE (June 19, 2024) : Added v16 as impacted. Updated description to clarify the attack vector. Late privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker's roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker's materialized view.

以上保留官方英文漏洞说明。

本分支修复于：14.11。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.11：加强 REFRESH MATERIALIZED VIEW CONCURRENTLY 中的安全限制

Documentation says the pg_signal_backend role cannot signal "a backend owned by a superuser". On the contrary, it can signal background workers, including the logical replication launcher. It can signal autovacuum workers and the autovacuum launcher. Signaling autovacuum workers and those two launchers provides no meaningful exploit, so exploiting this vulnerability requires a non-core extension with a less-resilient background worker. For example, a non-core background worker that does not auto-restart would experience a denial of service with respect to that particular background worker. The PostgreSQL project thanks Hemanth Sandrana and Mahendrakar Srinivasarao for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.10。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L

发布说明中的提及：

• 14.10：防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号

While modifying certain SQL array values, missing overflow checks let authenticated database users write arbitrary bytes to a memory area that facilitates arbitrary code execution. Missing overflow checks also let authenticated database users read a wide area of server memory. The CVE-2021-32027 fix covered some attacks of this description, but it missed others. The PostgreSQL project thanks Pedro Gallegos for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.10。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.13：检测计算新数组维度时的另一个整数溢出情况
• 14.10：检测计算新数组维度时的整数溢出

Certain aggregate function calls receiving "unknown"-type arguments could disclose bytes of server memory from the end of the "unknown"-type value to the next zero byte. One typically gets an "unknown"-type value via a string literal having no type designation. We have not confirmed or ruled out viability of attacks that arrange for presence of notable, confidential information in disclosed bytes. The PostgreSQL project thanks Jingzhou Fu for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.10。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.10：修复 DISTINCT "any" 聚合函数中对未知类型参数的处理

An extension script is vulnerable if it uses @extowner@ , @extschema@ , or @extschema:...@ inside a quoting construct (dollar quoting, '' , or "" ). No bundled extension is vulnerable. Vulnerable uses do appear in a documentation example and in non-bundled extensions. Hence, the attack prerequisite is an administrator having installed files of a vulnerable, trusted, non-bundled extension. Subject to that prerequisite, this enables an attacker having database-level CREATE privilege to execute arbitrary code as the bootstrap superuser. PostgreSQL will block this attack in the core server, so there's no need to modify individual extensions. The PostgreSQL project thanks Micah Gates, Valerie Woolard, Tim Carey-Smith, and Christoph Berg for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.9。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.9：如果模式或所有者名称包含引号、反斜杠或美元符号，则不允许将其替换到扩展脚本中

While CVE-2016-2193 fixed most interaction between row security and user ID changes, it missed a scenario involving function inlining. This leads to potentially incorrect policies being applied in 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 happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLE s. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. The PostgreSQL project thanks Wolfgang Walther for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.8。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

发布说明中的提及：

• 14.8：在内联集合返回函数后正确执行行级安全策略

This enabled an attacker having database-level CREATE privilege to execute arbitrary code as the bootstrap superuser. Database owners have that right by default, and explicit grants may extend it to other users. The PostgreSQL project thanks Alexander Lakhin for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.8。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.8：防止 CREATE SCHEMA 绕过 search_path 的更改

A modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. When a libpq client application has a Kerberos credential cache and doesn't explicitly disable option gssencmode , a server can cause libpq to over-read and report an error message containing uninitialized bytes from and following its receive buffer. If libpq's caller somehow makes that message accessible to the attacker, this achieves a disclosure of the over-read bytes. We have not confirmed or ruled out viability of attacks that arrange for a crash or for presence of notable, confidential information in disclosed bytes. The PostgreSQL project thanks Jacob Champion for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.7。组件：client。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.7：libpq 在 GSSAPI 传输加密初始化失败后可能泄漏内存内容

Some extensions use CREATE OR REPLACE or CREATE IF NOT EXISTS commands. Some don't adhere to the documented rule to target only objects known to be extension members already. An attack requires permission to create non-temporary objects in at least one schema, ability to lure or wait for an administrator to create or update an affected extension in that schema, and 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, the attacker can run arbitrary code as the victim role, which may be a superuser. Known-affected extensions include both PostgreSQL-bundled and non-bundled extensions. PostgreSQL is blocking this attack in the core server, so there's no need to modify individual extensions. The PostgreSQL project thanks Sven Klemm for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.5。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.5：不允许扩展脚本替换不属于该扩展的已有对象

Autovacuum, REINDEX , CREATE INDEX , REFRESH MATERIALIZED VIEW , CLUSTER , and pg_amcheck made incomplete efforts to operate safely when a privileged user is maintaining another user's objects. Those commands activated relevant protections too late or not at all. An attacker having permission to create non-temp objects in at least one schema could execute arbitrary SQL functions under a superuser identity. While promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum, not manually running the above commands, and not restoring from output of the pg_dump command. Performance may degrade quickly under this workaround. VACUUM is safe, and all commands are fine when a trusted user owns the target object. The PostgreSQL project thanks Alexander Lakhin for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.3。组件：core server。

官方受影响分支记录：14。

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.5：修复 CREATE INDEX 中的权限检查
• 14.3：将更多操作限制在“安全受限操作”沙箱内

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. If more preconditions hold, the attacker can exfiltrate the client's password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client's intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to CVE-2021-23214 . As with any exploitation of CVE-2021-23214 , the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to CVE-2021-23214 . The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient). The PostgreSQL project thanks Jacob Champion for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.1。组件：client。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.1：使 libpq 在 SSL 或 GSS 加密握手后拒绝多余的数据

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. This is similar to CVE-2011-0411 (different product). The PostgreSQL project thanks Jacob Champion for reporting this problem.

以上保留官方英文漏洞说明。

本分支修复于：14.1。组件：core server。

官方受影响分支记录：14。

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

发布说明中的提及：

• 14.1：使服务器在 SSL 或 GSS 加密握手后拒绝多余的数据
• 14.1：使 libpq 在 SSL 或 GSS 加密握手后拒绝多余的数据

尚未记录本分支的修复版本。组件：core server。

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

发布说明中的提及：

• 14.19：加强规划器估算函数中的安全检查

尚未记录本分支的修复版本。

发布说明中的提及：

• 14.19：在 pg_dump 输出的注释中，将名称中包含的换行符转换为空格