Headline
GHSA-qv35-3gw6-8q4j: In regclient, pinned manifest digests may be ignored
Impact
A malicious registry could return a different digest for a pinned manifest without detection.
Patches
This has been fixed in the v0.7.1 release.
Workarounds
After running a regclient.ManifestGet
, the returned digest can be compared to the requested digest.
Skip to content
Navigation Menu
Actions
Automate any workflow
Packages
Host and manage packages
Security
Find and fix vulnerabilities
Codespaces
Instant dev environments
GitHub Copilot
Write better code with AI
Code review
Manage code changes
Issues
Plan and track work
Discussions
Collaborate outside of code
Explore
- Learning Pathways
- White papers, Ebooks, Webinars
- Customer Stories
- Partners
GitHub Sponsors
Fund open source developers
* The ReadME Project
GitHub community articles
Enterprise platform
AI-powered developer platform
- Pricing
Provide feedback
Saved searches****Use saved searches to filter your results more quickly
Sign up
- GitHub Advisory Database
- GitHub Reviewed
- GHSA-qv35-3gw6-8q4j
In regclient, pinned manifest digests may be ignored
Moderate severity GitHub Reviewed Published Aug 3, 2024 in regclient/regclient • Updated Aug 5, 2024
Package
gomod github.com/regclient/regclient (Go)
Affected versions
< 0.7.1
Description
Impact
A malicious registry could return a different digest for a pinned manifest without detection.
Patches
This has been fixed in the v0.7.1 release.
Workarounds
After running a regclient.ManifestGet, the returned digest can be compared to the requested digest.
References
- GHSA-qv35-3gw6-8q4j
- regclient/regclient@7d17cff
Published to the GitHub Advisory Database
Aug 5, 2024