data/reports: fix GO-2026-5064, remove incorrect unversioned v1 containerd entry - #6239
Open
paul-sher-ec wants to merge 1 commit into
Open
data/reports: fix GO-2026-5064, remove incorrect unversioned v1 containerd entry#6239paul-sher-ec wants to merge 1 commit into
paul-sher-ec wants to merge 1 commit into
Conversation
…inerd entry github.com/containerd/containerd (v1, pre-/v2 rename) was listed with only vulnerable_at: 1.7.33 and no versions:. Per doc/format.md, omitting versions means every version of the module is vulnerable with no known fix - that's what was producing the incorrect 'all versions, unfixed' classification (visible in the generated OSV record as an unbounded 'introduced: "0"' range with no fix event). This is not just imprecise, it's wrong: - The GHSA (GHSA-33vj-92qq-66hc) and containerd's own advisory list only github.com/containerd/containerd/v2, with ranges 2.1.0-2.1.9, 2.2.0-2.2.5, 2.3.0-2.3.2. - The vulnerable functionality (CRI-level checkpoint/restore) was introduced in containerd v2.1.0 ("Support container restore through CRI/Kubernetes", containerd#10365) and does not exist in the 1.x line at all, so v1 isn't affected with an unknown fix - it's simply not affected. - doc/format.md documents no unaffected/not_affected field; the convention for a module that isn't hit is to omit its entry, which this change does. Regenerated data/osv/GO-2026-5064.json via 'vulnreport osv' to match. Fixes golang#5780
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5780.
github.com/containerd/containerd(v1, pre-/v2rename) was listed with onlyvulnerable_at: 1.7.33and noversions:. Perdoc/format.md, omittingversionsmeans "every version of the module is vulnerable, no known fix" — that's what was producing the reported "all versions, unfixed" classification. It's visible concretely in the previously-generated OSV record: an unbounded"introduced": "0"range for the v1 package with no matching fix event.This isn't just imprecise, it's incorrect:
github.com/containerd/containerd/v2, with ranges 2.1.0–2.1.9, 2.2.0–2.2.5, 2.3.0–2.3.2.doc/format.mddocuments nounaffected/not_affectedfield; the convention for a module that isn't hit is to omit its entry, which this PR does.data/osv/GO-2026-5064.jsonwas regenerated viavulnreport osvto match; no other fields changed.