# SUSE-SU-2023:4672-1: Security update for suse-build-key > This update replaces the build key import mechanism with a systemd service to ensure proper key management for SUSE Linux Enterprise. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Dec 2023 ## What is SUSE-SU-2023:4672-1? SUSE-SU-2023:4672-1 is a vulnerability in suse-build-key, published on 6 Dec 2023. ### Official description This update for suse-build-key fixes the following issues: This update runs a import-suse-build-key script. The previous libzypp-post-script based installation is replaced with a systemd timer and service (bsc#1217215 bsc#1216410 jsc#PED-2777). - suse-build-key-import.service - suse-build-key-import.timer It imports the future SUSE Linux Enterprise 15 4096 bit RSA key primary and reserve keys. After successful import the timer is disabled. To manually import them you can also run: # rpm --import /usr/lib/rpm/gnupg/keys/gpg-pubkey-3fa1d6ce-63c9481c.asc # rpm --import /usr/lib/rpm/gnupg/keys/gpg-pubkey-d588dc46-63c939db.asc ## Which versions are affected by SUSE-SU-2023:4672-1? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `suse-build-key` | SUSE:Enterprise Storage 7.1 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Micro 5.1 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Micro 5.2 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Micro 5.3 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Micro 5.4 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Micro 5.5 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | openSUSE:Leap 15.4 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | openSUSE:Leap 15.5 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | openSUSE:Leap Micro 5.3 | All versions | 12.0-150000.8.37.1 | | `suse-build-key` | openSUSE:Leap Micro 5.4 | All versions | 12.0-150000.8.37.1 | ## How do I fix SUSE-SU-2023:4672-1? Apply the vendor's patch. ## Is SUSE-SU-2023:4672-1 being exploited? There is no known exploitation of SUSE-SU-2023:4672-1 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for SUSE-SU-2023:4672-1 and fix it if it is affected. What it is: SUSE-SU-2023:4672-1 is a vulnerability in suse-build-key, published on 6 Dec 2023. Exploitation: There is no known exploitation of SUSE-SU-2023:4672-1 in the wild and no public exploit code. Affected product: suse-build-key. 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-2023-4672-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-4672-1/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/SUSE-SU-2023:4672-1 --- From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2023-4672-1/ Summaries are generated and may contain mistakes; the official description above is the record.