# SUSE-SU-2018:3074-1: Security update for postgresql10 - **Severity:** Not scored - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 8 Oct 2018 ## What is SUSE-SU-2018:3074-1? SUSE-SU-2018:3074-1 is a vulnerability in postgresql-init, published on 8 Oct 2018. ### Official description This update for brings postgresql10 version 10.5 to SUSE Linux Enterprise 12 SP3. (FATE#325659 bnc#1108308) This release marks the change of the versioning scheme for PostgreSQL to a 'x.y' format. This means the next minor releases of PostgreSQL will be 10.1, 10.2, ... and the next major release will be 11. * Logical Replication Logical replication extends the current replication features of PostgreSQL with the ability to send modifications on a per-database and per-table level to different PostgreSQL databases. Users can now fine-tune the data replicated to various database clusters and will have the ability to perform zero-downtime upgrades to future major PostgreSQL versions. * Declarative Table Partitioning Table partitioning has existed for years in PostgreSQL but required a user to maintain a nontrivial set of rules and triggers for the partitioning to work. PostgreSQL 10 introduces a table partitioning syntax that lets users easily create and maintain range and list partitioned tables. * Improved Query Parallelism PostgreSQL 10 provides better support for parallelized queries by allowing more parts of the query execution process to be parallelized. Improvements include additional types of data scans that are parallelized as well as optimizations when the data is recombined, such as pre-sorting. These enhancements allow results to be returned more quickly. * Quorum Commit for Synchronous Replication PostgreSQL 10 introduces quorum commit for synchronous replication, which allows for flexibility in how a primary database receives acknowledgement that changes were successfully written to remote replicas. ## Which versions are affected by SUSE-SU-2018:3074-1? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql-init` | SUSE:Enterprise Storage 4 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Enterprise Storage 4 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Enterprise Storage 4 | All versions | 10.5-1.3.1 | | `postgresql10` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 10.5-1.3.1 | | `postgresql10-libs` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 10.5-1.3.1 | | `postgresql-init` | SUSE:OpenStack Cloud 7 | All versions | 10-17.20.1 | | `postgresql10` | SUSE:OpenStack Cloud 7 | All versions | 10.5-1.3.2 | | `postgresql10-libs` | SUSE:OpenStack Cloud 7 | All versions | 10.5-1.3.1 | ## How do I fix SUSE-SU-2018:3074-1? Upgrade to a fixed version. ## Is SUSE-SU-2018:3074-1 being exploited? There is no known exploitation of SUSE-SU-2018:3074-1 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for SUSE-SU-2018:3074-1 and fix it if it is affected. What it is: SUSE-SU-2018:3074-1 is a vulnerability in postgresql-init, published on 8 Oct 2018. Exploitation: There is no known exploitation of SUSE-SU-2018:3074-1 in the wild and no public exploit code. Affected product: postgresql-init. 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-2018-3074-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-3074-1/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/SUSE-SU-2018:3074-1 --- From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2018-3074-1/ Summaries are generated and may contain mistakes; the official description above is the record.