Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/docker/distribution to v2.8.2+incompatible [SECURITY] #219

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/docker/distribution v2.8.1+incompatible -> v2.8.2+incompatible age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-2253

Impact

Systems that run distribution built after a specific commit running on memory-restricted environments can suffer from denial of service by a crafted malicious /v2/_catalog API endpoint request.

Patches

Upgrade to at least 2.8.2-beta.1 if you are running v2.8.x release. If you use the code from the main branch, update at least to the commit after f55a6552b006a381d9167e328808565dd2bf77dc.

Workarounds

There is no way to work around this issue without patching. Restrict access to the affected API endpoint: see the recommendations section.

References

/v2/_catalog endpoint accepts a parameter to control the maximum amount of records returned (query string: n).

When not given the default n=100 is used. The server trusts that n has an acceptable value, however when using a
maliciously large value, it allocates an array/slice of n of strings before filling the slice with data.

This behaviour was introduced ~7yrs ago [1].

Recommendation

The /v2/_catalog endpoint was designed specifically to do registry syncs with search or other API systems. Such an endpoint would create a lot of load on the backend system, due to overfetch required to serve a request in certain implementations.

Because of this, we strongly recommend keeping this API endpoint behind heightened privilege and avoiding leaving it exposed to the internet.

For more information

If you have any questions or comments about this advisory:

[1] faulty commit


Release Notes

docker/distribution (github.com/docker/distribution)

v2.8.2+incompatible

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from ulucinar as a code owner September 25, 2024 14:58
@renovate renovate bot added the automated label Sep 25, 2024
@renovate renovate bot requested a review from sergenyalcin as a code owner September 25, 2024 14:58
@renovate renovate bot changed the title Update module github.com/docker/distribution to v2.8.2+incompatible [SECURITY] Update module github.com/docker/distribution to v2.8.2+incompatible [SECURITY] - autoclosed Sep 25, 2024
@renovate renovate bot closed this Sep 25, 2024
@renovate renovate bot deleted the renovate/go-github.com-docker-distribution-vulnerability branch September 25, 2024 16:06
@renovate renovate bot restored the renovate/go-github.com-docker-distribution-vulnerability branch September 26, 2024 19:27
@renovate renovate bot changed the title Update module github.com/docker/distribution to v2.8.2+incompatible [SECURITY] - autoclosed Update module github.com/docker/distribution to v2.8.2+incompatible [SECURITY] Sep 26, 2024
@renovate renovate bot reopened this Sep 26, 2024
@renovate renovate bot force-pushed the renovate/go-github.com-docker-distribution-vulnerability branch from d02d13b to 26df8a5 Compare September 26, 2024 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants