# SUSE-SU-2025:03170-1: Security update for regionServiceClientConfigEC2

> Update for regionServiceClientConfigEC2 addresses SSL certificate compatibility and dependency changes for SLE 16.

- **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:** 11 Sep 2025

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

SUSE-SU-2025:03170-1 is a vulnerability in regionServiceClientConfigEC2, published on 11 Sep 2025. 

### Official description

This update for regionServiceClientConfigEC2 contains the following fixes:

- Update to version 5.0.0. (bsc#1246995)
  + SLE 16 python-requests requires SSL v3 certificates. Update 2
    region server certs to support SLE 16 when it gets released.

- Update dependency to accomodate metadata binary package name change
  in SLE 16. (bsc#1243419)

  + New 4096 certificate for rgnsrv-ec2-us-east1

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `regionServiceClientConfigEC2` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 5.0.0-4.37.1 |

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2025:03170-1 is a vulnerability in regionServiceClientConfigEC2, published on 11 Sep 2025. 
Exploitation: There is no known exploitation of SUSE-SU-2025:03170-1 in the wild and no public exploit code.

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

## Sources

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

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