# SUSE-SU-2020:3343-1: Security update for postgresql, postgresql96, postgresql10 and postgresql12 > Security update for PostgreSQL database packages on SUSE Linux Enterprise, addressing multiple vulnerabilities across various versions. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not stated - **Attackable:** Not stated - **Victim action needed:** Not stated - **Fix available:** Yes - **Published:** 16 Nov 2020 ## What is SUSE-SU-2020:3343-1? SUSE-SU-2020:3343-1 is a vulnerability in postgresql, published on 16 Nov 2020. ### Official description This update changes the internal packaging for postgresql, and so contains all currently maintained postgresql versions across our SUSE Linux Enterprise 12 products. * postgresql12 is shipped new in version 12.3 (bsc#1171924). The server and client packages only on SUSE Linux Enterprise Server 12 SP5, the libraries on SUSE Linux Enterprise Server 12 SP2 LTSS up to 12 SP5. + https://www.postgresql.org/about/news/2038/ + https://www.postgresql.org/docs/12/release-12-3.html * postgresql10 is updated to 10.13 (bsc#1171924). On SUSE Linux Enterprise Server 12 SP2 LTSS up to 12 SP5. + https://www.postgresql.org/about/news/2038/ + https://www.postgresql.org/docs/10/release-10-13.html * postgresql96 is updated to 9.6.18 (bsc#1171924): + https://www.postgresql.org/about/news/2038/ + https://www.postgresql.org/docs/9.6/release-9-6-18.html On SUSE Linux Enterprise Server 12-SP2 and 12-SP3 LTSS only. * postgresql 9.4 is updated to 9.4.26: + https://www.postgresql.org/about/news/2011/ + https://www.postgresql.org/docs/9.4/release-9-4-26.html + https://www.postgresql.org/about/news/1994/ + https://www.postgresql.org/docs/9.4/release-9-4-25.html ## Which versions are affected by SUSE-SU-2020:3343-1? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql` | SUSE:Enterprise Storage 5 | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Enterprise Storage 5 | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Enterprise Storage 5 | All versions | 12.4-3.5.1 | | `postgresql96` | SUSE:Enterprise Storage 5 | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:HPE Helion OpenStack 8 | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:HPE Helion OpenStack 8 | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:HPE Helion OpenStack 8 | All versions | 12.4-3.5.1 | | `postgresql96` | SUSE:HPE Helion OpenStack 8 | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 12.4-3.5.1 | | `postgresql94` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 9.4.26-24.3.1 | | `postgresql96` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 12.4-3.5.1 | | `postgresql94` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 9.4.26-24.3.1 | | `postgresql96` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 12.4-3.5.1 | | `postgresql96` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 12.4-3.5.1 | | `postgresql96` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 12.4-3.5.1 | | `postgresql` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 12.4-3.5.1 | | `postgresql` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 12.4-3.5.1 | | `postgresql94` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9.4.26-24.3.1 | | `postgresql96` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 9.6.19-6.4.1 | | `postgresql` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 12.0.1-4.4.1 | | `postgresql10` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 10.14-4.4.1 | | `postgresql12` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 12.4-3.5.1 | ## How do I fix SUSE-SU-2020:3343-1? Apply the vendor's patch. ## Is SUSE-SU-2020:3343-1 being exploited? There is no known exploitation of SUSE-SU-2020:3343-1 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for SUSE-SU-2020:3343-1 and fix it if it is affected. What it is: SUSE-SU-2020:3343-1 is a vulnerability in postgresql, published on 16 Nov 2020. Exploitation: There is no known exploitation of SUSE-SU-2020:3343-1 in the wild and no public exploit code. Affected product: postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/SUSE-SU-2020-3343-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-3343-1/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/SUSE-SU-2020:3343-1 --- From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2020-3343-1/ Summaries are generated and may contain mistakes; the official description above is the record.