SUSE-RU-2024:0725-1: Recommended update for suse-build-key

Published Feb 29, 2024
·
Updated

This update for suse-build-key fixes the following issues: Switch container key to be default RSA 4096bit. (jsc#PED-2777) run import script also in %posttrans section, but only when libzypp is not active. bsc#1219189 bsc#1219123

Affected Software

54 affected componentsFixes available
All of the following
SUSE openSUSE Leap Micro 5.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE openSUSE Leap Micro 5.4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE openSUSE Leap 15.5 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro for Rancher 5.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro 5.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro for Rancher 5.4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro 5.4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro 5.5 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE Basesystem Module 15-SP5 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server for SAP Applications 15 SP2 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server for SAP Applications 15 SP3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Server for SAP Applications 15 SP4 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Manager Proxy 4.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Manager Retail Branch Server 4.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Manager Server 4.3 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Enterprise Storage 7.1 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro 5.1 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro 5.2 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1
All of the following
SUSE SUSE Linux Enterprise Micro for Rancher 5.2 (noarch)
suse/suse-build-key<12.0-150000.8.43.1
12.0-150000.8.43.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade suse/suse-build-key to a version that resolves this vulnerability.

    Fixed in 12.0-150000.8.43.1
  2. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Micro-5.3-2024-725
  3. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Micro-5.4-2024-725
  4. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Micro-5.5-2024-725
  5. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Module-Basesystem-15-SP5-2024-725
  6. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-HPC-15-SP2-LTSS-2024-725
  7. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-HPC-15-SP3-LTSS-2024-725
  8. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-HPC-15-SP4-ESPOS-2024-725
  9. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-HPC-15-SP4-LTSS-2024-725
  10. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLED-15-SP4-LTSS-2024-725
  11. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES-15-SP2-LTSS-2024-725
  12. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES-15-SP3-LTSS-2024-725
  13. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES-15-SP4-LTSS-2024-725
  14. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES_SAP-15-SP2-2024-725
  15. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES_SAP-15-SP3-2024-725
  16. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES_SAP-15-SP4-2024-725
  17. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SUSE-Manager-Proxy-4.3-2024-725
  18. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SUSE-Manager-Retail-Branch-Server-4.3-2024-725
  19. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SUSE-Manager-Server-4.3-2024-725
  20. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SUSE-MicroOS-5.1-2024-725
  21. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-SUSE-MicroOS-5.2-2024-725
  22. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch SUSE-Storage-7.1-2024-725
  23. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch openSUSE-Leap-Micro-5.3-2024-725
  24. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch openSUSE-Leap-Micro-5.4-2024-725
  25. Upgrade

    Upgrade suse-build-key to a version that resolves this vulnerability.

    Patch openSUSE-SLE-15.5-2024-725
  26. Configuration

    Switch the container key to be the default RSA 4096-bit key.

    suse-build-key container key algorithm and size = RSA 4096-bit

Event History

Feb 29, 2024
Advisory Published
via SUSE·12:30 PM

Frequently Asked Questions

1

Which systems are covered by this update?

The update applies to suse-build-key on openSUSE Leap Micro 5.3 and 5.4, openSUSE Leap 15.5, SUSE Linux Enterprise Micro 5.3 and 5.4, and SUSE Linux Enterprise Micro for Rancher 5.3 and 5.4.

2

What changes if the update cannot be installed immediately?

The update changes the container key default to RSA 4096-bit and ensures the import script can run during %posttrans when libzypp is not active. The provided data does not specify an alternative mitigation or workaround.

3

Does the update alter package-installation behavior?

Yes. It runs the import script in the %posttrans section, but only when libzypp is not active.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203