# SUSE-SU-2025:20224-1: Security update for cloud-regionsrv-client, python-toml

> Security update for cloud-regionsrv-client and python-toml addressing various bugs and configuration issues in SUSE cloud environments.

- **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:** 20 Feb 2025

## What is SUSE-SU-2025:20224-1?

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

### Official description

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

cloud-regionsrv-client: 
- 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

python-toml: 
-  Includes python311-toml as dependency for cloud-regionsrv-client

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cloud-regionsrv-client` | SUSE:Linux Micro 6.1 | All versions | 10.3.11-slfo.1.1_2.1 |
| `python-toml` | SUSE:Linux Micro 6.1 | All versions | 0.10.2-slfo.1.1_1.2 |

## How do I fix SUSE-SU-2025:20224-1?

Upgrade to a fixed version.

## Is SUSE-SU-2025:20224-1 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2025:20224-1 and fix it if it is affected.

What it is: SUSE-SU-2025:20224-1 is a vulnerability in cloud-regionsrv-client, published on 20 Feb 2025. 
Exploitation: There is no known exploitation of SUSE-SU-2025:20224-1 in the wild and no public exploit code.

Affected product: cloud-regionsrv-client. 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-2025-20224-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20224-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:20224-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2025-20224-1/
Summaries are generated and may contain mistakes; the official description above is the record.