Skip to content

chore(deps): update module github.com/sigstore/sigstore-go to v1.2.0 [security] (alauda-v0.41.1) - #186

Open
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v0.41.1from
renovate/alauda-v0.41.1-go-github.com-sigstore-sigstore-go-vulnerability
Open

chore(deps): update module github.com/sigstore/sigstore-go to v1.2.0 [security] (alauda-v0.41.1)#186
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v0.41.1from
renovate/alauda-v0.41.1-go-github.com-sigstore-sigstore-go-vulnerability

Conversation

@alaudaa-renovate

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
github.com/sigstore/sigstore-go v1.1.4 -> v1.2.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


sigstore-go has a multi-log threshold bypass via single compromised log

CVE-2026-49834 / GHSA-9vcr-p3rj-q5q6

More information

Details

Impact

What kind of vulnerability is it? Who is impacted?

A verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.

As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.

Note that this does not affect Cosign, as Cosign sets a threshold of 1.

Patches

Has the problem been patched? What versions should users upgrade to?

Upgrade to v1.1.5.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

There is no workaround, beyond relying on trusted logs.

Severity

  • CVSS Score: 5.9 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sigstore/sigstore-go (github.com/sigstore/sigstore-go)

v1.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: sigstore/sigstore-go@v1.1.4...v1.2.0


Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, 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 has been generated by Renovate Bot.

@alaudaa-renovate

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: github.com/tektoncd/cli/pkg/chain imports
	github.com/tektoncd/chains/pkg/chains/storage imports
	github.com/tektoncd/chains/pkg/chains/storage/docdb imports
	gocloud.dev/docstore/awsdynamodb: cannot find module providing package gocloud.dev/docstore/awsdynamodb
go: warning: go.step.sm/crypto@v0.77.7: retracted by module author: unintentional releases tagged from non-master branch
go: to switch to the latest unretracted version, run:
	go get go.step.sm/crypto@latest

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.

1 participant