Target allocator docker docker client not affected#15
Merged
Conversation
These three HIGH CVEs apply to the Moby server (AuthZ plugin bypass, docker cp PATH RCE, docker cp bind-mount TOCTOU). The quay.io/stackstate/opentelemetry-target-allocator image only links the client-side packages of github.com/docker/docker via github.com/prometheus/prometheus/discovery; the Moby server (dockerd, daemon, api/server) is not present in the binary and no Docker daemon runs in the image. Add a Lane 2 OpenVEX statement scoped to this image only — we have not audited goreleaser's docker/docker reachability, so the existing goreleaser exception in docker-images is left in place. Upstream tracker: open-telemetry/opentelemetry-operator#4926 confirms the operator and target allocator use only the docker client side and that prometheus/prometheus#18433 has already removed the legacy docker/docker dependency in Prometheus. Once the next prometheus-operator release picks up that Prometheus version and the OpenTelemetry Operator bumps to it, this dependency disappears from the target allocator entirely.
CVE-2026-33997 is an off-by-one error in the Moby server's plugin privilege validation (docker plugin install). Like the other three docker/docker findings on this image it is server-side only, while the target allocator binary links only the client-side packages of github.com/docker/docker through github.com/prometheus/prometheus/discovery. Same not_affected / vulnerable_code_not_in_execute_path justification, appended to the existing image-scoped statement.
…ents Add a status_notes field on each of the four not_affected statements recording a 6-week review-by date (2026-07-29). The VEX is conditional on the next prometheus-operator release dropping the legacy github.com/docker/docker dependency once it picks up the Prometheus release that landed prometheus/prometheus#18433; if that release has not shipped by the deadline, re-check and either extend the note or retire the statement once the OpenTelemetry Operator has bumped past it. OpenVEX v0.2.0 has no first-class expires field, so the deadline is encoded in status_notes (free text, same field jetty-http uses).
deontaljaard
approved these changes
Jun 17, 2026
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
2 participants
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.
No description provided.