SUSE-SU-2025:20123-1 Security update for cloud-regionsrv-client

Not scored Published

Security update for cloud-regionsrv-client fixing registration, sudo permissions, and registry cleanup issues.

Exploited in the wild
Not known
Login needed
Not stated
Attackable
Not stated
Victim action needed
Not stated
Fix
Available

What is SUSE-SU-2025:20123-1?

SUSE-SU-2025:20123-1 is a vulnerability in cloud-regionsrv-client, published on 10 Feb 2025.

Official description

This update for cloud-regionsrv-client contains the following fixes:

  • Update to 10.3.11 (bsc#1234050)

    • Send registration code for the extensions, not only base product
  • Update to 10.3.9: (bsc#1234050)

    • Send registration code for the extensions, not only base product
  • Update to 10.3.8: (bsc#1233333)

    • Fix the package requirements for cloud-regionsrv-client
    • Follow changes to suseconnect error reporting from stdout to stderr
  • Update to 10.3.7: (bsc#1232770)

    • Fix the product triplet for LTSS, it is always SLES-LTSS, not $BASEPRODUCT-LTSS
  • Update to 10.3.6: (jsc#PCT-471, bsc#1230615)

    • Fix sudo setup ~ permissions cloudguestregistryauth ~ directory ownership /etc/sudoers.d
    • spec file ~ Remove traces of registry related entries on SLE 12
    • Forward port ~ fix for sles12 disable registry ~ fix for sles12 no trans_update
    • Deregister non free extensions at registercloudguest –clean
    • Fix registry cleanup at registercloudguest –clean, don't remove files
    • Prevent duplicate search entries in registry setup
  • Update EC2 plugin to 1.0.5

    • Switch to using the region endpoint from IMDS to determine the region instead of deriving the data from the availability zone
  • Update to 10.3.5:

    • Update spec file to build in all code streams and have proper dependencies.
  • Update to 10.3.4:

    • Modify the message when network access over a specific IP version does not work. This is an informational message and should not look like an error
    • Inform the user that LTSS registration takes a little longer
    • fix for sles12 no transactional update:
      • SLE 12 family has no products with transactional-update we do not need to look for this condition
  • From 10.3.3: (bsc#1229472)

    • Handle changes in process structure to properly identify the running zypper parent process and only check for 1 PID
  • From 10.3.2:

    • Remove rgnsrv-clnt-fix-docker-setup patch included upstream
  • From 10.3.1: (jsc#PCT-400)

    • Add support for LTSS registration
    • Add fix for sles12 disable registry issue: ~ No container support in SLE 12
  • Add fix for docker setup: (bsc#1229137)

    • The entry for the update infrastructure registry mirror was written incorrectly causing docker daemon startup to fail.
  • Update to version 10.3.0: (bsc#1227308, bsc#1222985)

    • Add support for sidecar registry Podman and rootless Docker support to set up the necessary configuration for the container engines to run as defined
    • Add running command as root through sudoers file

Which versions are affected by SUSE-SU-2025:20123-1?

Linux distribution packages (2)
cloud-regionsrv-client SUSE:Linux Micro 6.0All versions10.3.11-3.1
python-toml SUSE:Linux Micro 6.0All versions0.10.2-5.118

How do I fix SUSE-SU-2025:20123-1?

Upgrade to a fixed version.

Is SUSE-SU-2025:20123-1 being exploited?

There is no known exploitation of SUSE-SU-2025:20123-1 in the wild and no public exploit code.

Sources

Is SUSE-SU-2025:20123-1 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free