postgresql:15 security update
エラータID: AXSA:2026-1374:01
リリース日:
2026/07/29 Wednesday - 13:59
題名:
postgresql:15 security update
影響のあるチャネル:
MIRACLE LINUX 9 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- PostgreSQL には、整数オーバーフローの問題があるため、リモート
の攻撃者により、PostgreSQL を実行しているユーザーの権限での任意
のコードの実行、およびサービス拒否攻撃を可能とする脆弱性が存在
します。(CVE-2026-6473)
- PostgreSQL には、シンボリックリンクの解釈処理に問題があるため、
ローカルの攻撃者により、情報の漏洩、データ破壊、およびサービス
拒否攻撃を可能とする脆弱性が存在します。(CVE-2026-6475)
- PostgreSQL の libpq の lo_export() 関数、lo_read() 関数、
lo_lseek64() 関数、lo_tell64() 関数には、バッファオーバーフローの
問題があるため、リモートの攻撃者により、任意のコードの実行を可能
とする脆弱性が存在します。(CVE-2026-6477)
- PostgreSQL には、タイミングサイドチャネル攻撃が可能となって
しまう問題があるため、リモートの攻撃者により、情報の漏洩、および
データ破壊を可能とする脆弱性が存在します。(CVE-2026-6478)
Modularity name: postgresql
Stream name: 15
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2026-6473
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.
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.
CVE-2026-6475
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.
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.
CVE-2026-6477
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.
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.
CVE-2026-6478
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.
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.
追加情報:
N/A
ダウンロード:
SRPMS
- pgaudit-1.7.0-1.module+el9+1162+bd7b78e4.src.rpm
MD5: 4ff72737567bed879440c995c3387fb7
SHA-256: dd4abdf4e0e8c497f2b2808125beb0619826176a70ac67fa8de254a96e154877
Size: 51.24 kB - pg_repack-1.4.8-2.module+el9+1162+bd7b78e4.src.rpm
MD5: d48dbfa63b27fb6d5fa5b41b65873a97
SHA-256: 8e528fbc03a704700c24ce61445305b23a31406f75bce4ddd72928937341e5f4
Size: 102.34 kB - postgres-decoderbufs-1.9.7-1.Final.module+el9+1162+bd7b78e4.src.rpm
MD5: 154bb7f6dfaca0162af003cdd1173519
SHA-256: d29a6ea0d5c3f11794c9c8fce1437450f5d74fd9dbf36c5dc8e0b1c2f4502649
Size: 21.46 kB - postgresql-15.18-1.module+el9+1162+bd7b78e4.src.rpm
MD5: f7345b02225c4c0c720b43d58479e485
SHA-256: 8bd7ff6eb5683823f2acca5f4023e9e9374a45f6d28ce45d226d938331520b18
Size: 43.65 MB
Asianux Server 9 for x86_64
- pgaudit-1.7.0-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 928e1d86b5bd669f9b5aea4bf73bc445
SHA-256: 05856d8215a4b4a8b914b209d7ae18e7e6784420b3f8c746b96f918ff21b4c63
Size: 27.49 kB - pgaudit-debugsource-1.7.0-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 8753a1a950fd969874a876e2bb3d211f
SHA-256: dda34144dd4575932134282e18a99e3370622a8f0eadb6eb5a1dc8d40ea17c0e
Size: 22.29 kB - pg_repack-1.4.8-2.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: f235abeca3d6c12ae7ec43adffbfce69
SHA-256: 05acc2b6524cb321d34bd07bb0bc570bec9d9ab2cb357219f77e829b8aa5a922
Size: 90.95 kB - pg_repack-debugsource-1.4.8-2.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 62c8bdc75484f2bd2ecc6117390187a3
SHA-256: 86f30c5c4c5cd2819a12035dcd023099511003053e2d4ccad97d01f757fe5e34
Size: 48.09 kB - postgres-decoderbufs-1.9.7-1.Final.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 25a882918acaffd72cf7fc11cc1e88b9
SHA-256: a11ef2d33ddd64bce2ddff56da9be1a5b694f6aba5af55976cb12aed7a961e6a
Size: 22.72 kB - postgres-decoderbufs-debugsource-1.9.7-1.Final.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: c890dabb29e1f80343b0d9c9ee1cf0b9
SHA-256: 93727ea39af6fffee80d93fad69a2d5fd9df9ea8494e435d1ef95a12afaddf77
Size: 16.55 kB - postgresql-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 7b694e002e2b8bdd989cec4832721c88
SHA-256: f6653f13548c9528d0e34910a738ba619c83f419c60a9ca486684f69f8a50446
Size: 1.74 MB - postgresql-contrib-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 097a9e1dd03bef78942fd27ce2a330a2
SHA-256: 3b92b2de4af479bce787c2cd2fab6b6d6d4e06fd1a1eccde344dd27c3d0f8551
Size: 0.98 MB - postgresql-debugsource-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: b95783a878bdcf176c6e01f31713e14a
SHA-256: 788e9f8606a69df3b992e7a31a681b00ce22725169e4f026c401662fc6a5686e
Size: 16.20 MB - postgresql-docs-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: bdd260ba17b9ae7fd7db0557bc035aac
SHA-256: c035f08139c8fdd518f47d4fda31e5bca57120eb05d01dd19aecd91168b14efb
Size: 2.91 MB - postgresql-plperl-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 995cb8f7c0de3d9965859284e97428ce
SHA-256: 213022cc6cc144b5d728cca609e956a79bab5efbb458174f5b2aa346fdfaaa85
Size: 77.95 kB - postgresql-plpython3-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: ba4c00a5f29e41dbaccc131a81109507
SHA-256: bca2d63b7aa70b5deb6ee73819c55bd32cc7a7ec766c228e3f99a0f0d2382016
Size: 100.37 kB - postgresql-pltcl-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 16f4828a8318659f2948101ac6be08fe
SHA-256: 2389a177997560f1b3472794d88c86de893c5dca7b8a6620ce358d828e6d59ee
Size: 51.84 kB - postgresql-private-devel-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 7687183eabe10aa43f9c85de46af5823
SHA-256: 355a214ff57f11fb36920261200ef68d7a36d28def7ccf8843058f07520fed52
Size: 67.49 kB - postgresql-private-libs-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: d8d8d791cea04d4d578b3d0fe21d3664
SHA-256: d0d551af3ec978d5083374708bb10d895784a419a2b2a4d2ddb4cb2876ce492d
Size: 144.38 kB - postgresql-server-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 7303d3e77e55dae5096036908c273815
SHA-256: 9dfe8ab76b564595311090b590d99e0d459d8c5833157583554b9e30240930c6
Size: 6.30 MB - postgresql-server-devel-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 5f37ad559af5e7f64d4341aa8eea4420
SHA-256: 1369bb232d624d85ceb556f4630f103010572c64c1aa643b01c8ce539895fd60
Size: 1.46 MB - postgresql-static-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: d9a02cce4f6914aa4efdbccabbae8576
SHA-256: 32789d2ff9d899f10205ced6b597b18ddf23f15f67fd67ca4b325397417f7c41
Size: 130.54 kB - postgresql-test-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 8eb17d749e13d283656ef278ffd0bc8c
SHA-256: 8570497351f6957dbfd45171d129ccadb2e91f93f04dd400a3c8cf8d0888f342
Size: 1.73 MB - postgresql-test-rpm-macros-15.18-1.module+el9+1162+bd7b78e4.noarch.rpm
MD5: ac160fd54d27a5807ba3851dafe1c377
SHA-256: 89c0dc777ef7e71c4815977d1c643f6417ac3831352e076eda3f1a88c6e6773c
Size: 9.70 kB - postgresql-upgrade-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: d04e5a0910744de0c488bbfeeea4a2d2
SHA-256: 932ee5e2df0894214fa4ff9232cc280bb2c150f33831bb66a3cb8d26806f2ba1
Size: 4.77 MB - postgresql-upgrade-devel-15.18-1.module+el9+1162+bd7b78e4.x86_64.rpm
MD5: 94256ba709d8ebe9c37c340db1915232
SHA-256: ba0569c602d5de93c0fd0bbfd4055c08b51dfb7a4db62a5b833bea10abc84798
Size: 1.24 MB