# SUSE-SU-2022:3781-1: Security update for container-suseconnect

> Rebuild of container-suseconnect against updated Go compiler to address underlying security issues in the runtime environment.

- **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:** 26 Oct 2022

## What is SUSE-SU-2022:3781-1?

SUSE-SU-2022:3781-1 is a vulnerability in container-suseconnect, published on 26 Oct 2022. 

### Official description

This update of container-suseconnect is a rebuilt of the previous sources against the current security updated go compiler.

## Which versions are affected by SUSE-SU-2022:3781-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `container-suseconnect` | SUSE:Linux Enterprise Module for Containers 15 SP3 | All versions | 2.3.0-150000.4.19.2 |
| `container-suseconnect` | SUSE:Linux Enterprise Module for Containers 15 SP4 | All versions | 2.3.0-150000.4.19.2 |
| `container-suseconnect` | openSUSE:Leap 15.3 | All versions | 2.3.0-150000.4.19.2 |

## How do I fix SUSE-SU-2022:3781-1?

Upgrade to a fixed version.

## Is SUSE-SU-2022:3781-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2022:3781-1 is a vulnerability in container-suseconnect, published on 26 Oct 2022. 
Exploitation: There is no known exploitation of SUSE-SU-2022:3781-1 in the wild and no public exploit code.

Affected product: container-suseconnect. 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-2022-3781-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-3781-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:3781-1

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