Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Security: 3 oras-go CVEs + 1 x/text CVE, all reachable (govulncheck-confirmed) — proposing a dependency bump

オープン
  • 何か問題がありますか？
#306 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go
領域
build-system, ci-cd, security

調査の方向性

Start with go.mod and the reachable call sites in pkg/common/artifact/oci_artifact.go, pkg/commands/deploy_actions.go, and pkg/commands/keystore/create_keystore.go. Review the pinned Go versions in checks.yml, build.yml, tests.yml, golangci-lint.yml, create.yml, devnet.yml, e2e.yml, and release.yml, then run govulncheck ./..., go build ./..., go vet ./..., and make tests-fast. Done means the four reachable CVEs no longer appear and the relevant checks pass.

索引モデルが issue の本文から書いたものです。

説明

Hi — per the README's note to open an issue before a PR for significant changes, flagging this one first since the fix forces a go directive bump that touches every CI workflow's pinned Go version.

What govulncheck ./... found

go.mod currently pins oras.land/oras-go/v2 v2.3.1 and golang.org/x/text v0.26.0. Running govulncheck ./... against current main shows four reachable vulnerabilities (not just pinned-but-unused — the tool traces the call path back to this repo's own source):

oras-go (3 CVEs, all fixed in v2.6.1):

  • GO-2026-5885 / CVE-2026-48978 — malicious registry can hijack the Bearer-token realm to exfiltrate credentials/refresh tokens
  • GO-2026-5884 — registry credentials forwarded across redirects
  • GO-2026-5882 / CVE-2026-50151 — blob-upload credential forwarding via an unvalidated Location header

All three trace to the same call site:

pkg/common/artifact/oci_artifact.go:237:20: artifact.OCIArtifactBuilder.CreateEigenRuntimeArtifact
    calls oras.Copy, which eventually calls auth.Client.Do / remote.Repository.Push

x/text (1 CVE, fixed in v0.39.0):

  • GO-2026-5970 / CVE-2026-56852 — infinite loop on invalid input
pkg/commands/deploy_actions.go:507:75: commands.DeployL2ContractsAction calls cases.Caser.String, which eventually calls norm.Form.Properties
pkg/commands/keystore/create_keystore.go:86:47: keystore.CreateBLSKeystore calls keystore.SaveToKeystoreWithCurveType, which eventually calls norm.Form.String

The catch worth flagging before a PR

The lowest oras-go version that actually contains the fix is v2.6.1, and upstream bumped its own go directive to go 1.25.0 starting at that release (v2.6.0 is still go 1.23.0 but does not contain the fix). So clearing these CVEs unavoidably means bumping this repo's own go.mod from go 1.23.6 to go 1.25.0 — which is also required by the x/text fix version, so no second bump is needed once both land together.

This repo's CI pins Go 1.23/1.24 explicitly across every workflow (checks.yml, build.yml, tests.yml, golangci-lint.yml: 1.23; create.yml, devnet.yml, e2e.yml, release.yml: 1.24/1.24.2) — none at 1.25 yet. With GOTOOLCHAIN=auto (Go's default since 1.21) go build/go test on those runners should auto-fetch the 1.25 toolchain at CI time, but I wanted to say so explicitly rather than have it be a surprise, since you may prefer to bump actions/setup-go's pinned version in the same PR instead of relying on auto-toolchain-fetch.

What I've already verified in a scratch fork clone (not pushed anywhere yet)

  • go get oras.land/oras-go/[email protected] golang.org/x/[email protected] && go mod tidy — clean, no code changes required.
  • go build ./... and go vet ./... — clean.
  • make tests-fast (your own short-mode target) — all packages pass, including pkg/common/artifact and pkg/commands/keystore which exercise the changed code paths directly.
  • Re-ran govulncheck ./... post-bump — all four CVEs above drop out of the reachable set.

Happy to open the PR now if that sounds right, or adjust scope/approach first if you'd rather handle the go directive bump differently (e.g. bundling an actions/setup-go version bump in the same change).

主要言語
Go
スター
28
フォーク
11
30日以内にマージされた PR はありません

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Layr-Labs/devkit-cli のほかの issue

Layr-Labs/devkit-cli の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。