postgresql-13.18-1.el9_5
エラータID: AXSA:2024-9434:05
リリース日:
2024/12/19 Thursday - 22:50
題名:
postgresql-13.18-1.el9_5
影響のあるチャネル:
MIRACLE LINUX 9 for x86_64
Severity:
High
Description:
以下項目について対処しました。
[Security Fix]
- PostgreSQL には、クエリを再利用する際における誤った
行のセキュリティポリシーを適用してしまう問題があるため、
リモートの攻撃者により、行単位のセキュリティポリシーを
持つテーブルに対する特定のクエリや SQL 関数の実行を
介して、不正なデータの読み取りや更新を可能とする脆弱性
が存在します。(CVE-2024-10976)
- PostgreSQL には、リモートの攻撃者により、SET ROLE、
SET SESSION AUTHORIZATION、または同等の機能の利用を
介して、意図しない行の表示および更新を可能とする脆弱性
が存在します。(CVE-2024-10978)
- PostgreSQL の PL/Perl には、環境変数の処理の欠陥に
起因して PATH などの環境変数の変更を許容してしまう問題
があるため、権限のないリモートの攻撃者により、任意の
コードの実行を可能とする脆弱性が存在します。
(CVE-2024-10979)
解決策:
パッケージをアップデートしてください。
CVE:
CVE-2024-10976
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.
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.
CVE-2024-10978
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.
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.
CVE-2024-10979
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.
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.
追加情報:
N/A
ダウンロード:
SRPMS
- postgresql-13.18-1.el9_5.src.rpm
MD5: 6efecc2d2a47e54b87f213b7bdf3d76d
SHA-256: 45d3d98640ab09389b34b674c4b83158b99777e7dc3218ed43b8eb7d378cce15
Size: 48.78 MB
Asianux Server 9 for x86_64
- postgresql-13.18-1.el9_5.x86_64.rpm
MD5: a7aa97c21e19f59eff283d5dfb8378dd
SHA-256: 6db7e0f7b2bdff65fd9b500c3cc7da38008e3ed67505a12b266de35b8ac83638
Size: 1.58 MB - postgresql-contrib-13.18-1.el9_5.x86_64.rpm
MD5: ad9634d689d807c33deefd7fa7d825e7
SHA-256: 7bab0dfb50a221548c95e3b90f94b001f0fd80021805c418d5d2d00d2d2fda69
Size: 890.61 kB - postgresql-docs-13.18-1.el9_5.x86_64.rpm
MD5: 033189b2ffa18d30e339e5067cfcbef3
SHA-256: be827346af6fe84b7361e76f5199c3d797ade9017491902cb4540160c6f03437
Size: 9.60 MB - postgresql-plperl-13.18-1.el9_5.x86_64.rpm
MD5: 881bb096ef57ac32275f0762f5735e55
SHA-256: 0fb54e23ca00505a5d63d156d45dd7fdd2fbc61d8daeeef1aab93eeabf6c1e5c
Size: 74.23 kB - postgresql-plpython3-13.18-1.el9_5.x86_64.rpm
MD5: d0f2a65b53cec254e9f1541bc64a67e8
SHA-256: 8b97b5b4a8d03c3904ac29a2b502700338b3820e30cb6939785ae7519d428d0d
Size: 93.26 kB - postgresql-pltcl-13.18-1.el9_5.x86_64.rpm
MD5: 0e03f3071cb7bc751e68ac23b2b7f4aa
SHA-256: 531692638351ef03a1b834092a5915bacabc613ceb05871d5209f5b72efc471c
Size: 48.37 kB - postgresql-private-devel-13.18-1.el9_5.x86_64.rpm
MD5: d977927973df2a8faa12996cb6950919
SHA-256: 239107bfb95ddb5eea46b725e23cd4c1b13b08bda70de10cf29b853312851f9f
Size: 62.42 kB - postgresql-private-libs-13.18-1.el9_5.x86_64.rpm
MD5: 46a8316f715e9776236acc6f43cf726c
SHA-256: f30a341c0af9323e23151d58debf35bb8bd4693d638e2991167b600a0a7e992f
Size: 136.33 kB - postgresql-server-13.18-1.el9_5.x86_64.rpm
MD5: 594c8c6e39191a12bd978d9ef71c36dd
SHA-256: 7d0a6316bbe3d5a2f0f685665142977aeb5e33f27d44354eabc89599a5cee4db
Size: 5.78 MB - postgresql-server-devel-13.18-1.el9_5.x86_64.rpm
MD5: c5c8d68c9d49ab1f96a90f35db9409e5
SHA-256: 1fbac49c8ccdbfd312aacdd1c9764d90fe9c0f8ff3a2654528d1dda257fcd1a1
Size: 1.30 MB - postgresql-static-13.18-1.el9_5.x86_64.rpm
MD5: bee719ef61f45060ca0ea0dad736f3c9
SHA-256: 8efee0e3fa9799f190ed7ac51274931724ce0288f778b8c9efa2fbb89a95f241
Size: 124.58 kB - postgresql-test-13.18-1.el9_5.x86_64.rpm
MD5: 2c274c8850f284b85a9817793750b1c7
SHA-256: 41148ac84cde87dcd10191c1eca3bde3cdd0d442ef2ee04139861f607823b344
Size: 1.53 MB - postgresql-test-rpm-macros-13.18-1.el9_5.noarch.rpm
MD5: 4b89cc54940c8f657a2cebeae91d6f8b
SHA-256: c15815771614d1bac75a0305d0853d54b7b5dabd246b894b33c3734c8a1ddcdd
Size: 8.90 kB - postgresql-upgrade-13.18-1.el9_5.x86_64.rpm
MD5: c87b2d6ca6a9eccb758939fb05c15ee0
SHA-256: fbde32b1ff5262c866504cbee4748ebb9c807b5e74b31120353b440f64dece20
Size: 4.62 MB - postgresql-upgrade-devel-13.18-1.el9_5.x86_64.rpm
MD5: c7b69cd43f9213974fdb48dcb895b1fb
SHA-256: 55afc51a4b08a2340f15ea61661f50a02815a642e95997383cefe68eabc5fd38
Size: 1.20 MB