# SUSE-SU-2023:4974-1: Security update for distribution


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Dec 2023

## What is SUSE-SU-2023:4974-1?

SUSE-SU-2023:4974-1 is a vulnerability in distribution, published on 26 Dec 2023. 

### Official description

This update for distribution fixes the following issues:

distribution was updated to 2.8.3 (bsc#1216491):

* Pass `BUILDTAGS` argument to `go build`
* Enable Go build tags
* `reference`: replace deprecated function `SplitHostname`
* Dont parse errors as JSON unless Content-Type is set to JSON
* update to go 1.20.8
* Set `Content-Type` header in registry client `ReadFrom`
* deprecate reference package, migrate to github.com/distribution/reference
* `digestset`: deprecate package in favor of `go-digest/digestset`
* Do not close HTTP request body in HTTP handler

## Which versions are affected by SUSE-SU-2023:4974-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `distribution` | SUSE:Linux Enterprise Module for Containers 15 SP4 | All versions | 2.8.3-150400.9.24.1 |
| `distribution` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 2.8.3-150400.9.24.1 |
| `distribution` | openSUSE:Leap 15.4 | All versions | 2.8.3-150400.9.24.1 |
| `distribution` | openSUSE:Leap 15.5 | All versions | 2.8.3-150400.9.24.1 |

## How do I fix SUSE-SU-2023:4974-1?

Upgrade to a fixed version.

## Is SUSE-SU-2023:4974-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2023:4974-1 is a vulnerability in distribution, published on 26 Dec 2023. 
Exploitation: There is no known exploitation of SUSE-SU-2023:4974-1 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2023:4974-1

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