-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump github.com/sigstore/rekor from 1.1.2-0.20230508234306-ad288b385a44 to 1.2.0 #18709
build(deps): bump github.com/sigstore/rekor from 1.1.2-0.20230508234306-ad288b385a44 to 1.2.0 #18709
Conversation
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dependabot[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
dcb2759
to
715da73
Compare
@dependabot rebase |
Bumps [github.com/sigstore/rekor](https://github.com/sigstore/rekor) from 1.1.2-0.20230508234306-ad288b385a44 to 1.2.0. - [Release notes](https://github.com/sigstore/rekor/releases) - [Changelog](https://github.com/sigstore/rekor/blob/main/CHANGELOG.md) - [Commits](https://github.com/sigstore/rekor/commits/v1.2.0) --- updated-dependencies: - dependency-name: github.com/sigstore/rekor dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
715da73
to
388e70f
Compare
In case anybody else wonders WTF no renovate PR on this: I verified vulnerability alerts are being seen by renovate in the logs: {
"alerts": {
"go/github.com/sigstore/rekor": {
"< 1.2.0": "1.2.0"
}
}
} And it "knows" that an update is needed: {
"alertPackageRules": [
{
"matchDatasources": [
"go"
],
"matchPackageNames": [
"github.com/sigstore/rekor"
],
"matchCurrentVersion": "= 1.1.2-0.20230508234306-ad288b385a44",
"matchFiles": [
"go.mod"
],
"allowedVersions": "1.2.0",
"prBodyNotes": [
"### GitHub Vulnerability Alerts",
"#### [CVE-2023-33199](https://github.com/sigstore/rekor/security/advisories/GHSA-frqx-jfcm-6jjr)\n\n### Impact\nA malformed proposed entry of the `intoto/v0.0.2` type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal.\n\n### Patches\nThis is fixed in v1.2.0 of Rekor.\n\n### Workarounds\nNo\n\n### References\nDiscovered by OSS-Fuzz"
],
"isVulnerabilityAlert": true,
"force": {
"groupName": null,
"schedule": [],
"dependencyDashboardApproval": false,
"minimumReleaseAge": null,
"rangeStrategy": "update-lockfile",
"commitMessageSuffix": "[SECURITY]",
"branchTopic": "{{{datasource}}}-{{{depName}}}-vulnerability",
"prCreation": "immediate",
"labels": [
"dependencies",
"security"
]
}
}
]
} However, the logs then show that renovate is completely disabled for this dependency: {
"currentDigest": "ad288b385a44",
"currentValue": "v1.1.2-0.20230508234306-ad288b385a44",
"datasource": "go",
"depName": "github.com/sigstore/rekor",
"depType": "indirect",
"digestOneAndOnly": true,
"enabled": false,
"managerData": {
"lineNumber": 153,
"multiLine": true
},
"packageName": "github.com/sigstore/rekor",
"skipReason": "disabled",
"updates": []
}, Poking around trying to figure out why it's disabled, I noticed |
Opened containers/automation#143 |
I'm not sure w/n to believe this:
|
/hold |
Sadly, yes. It’s an ongoing struggle, and one we are likely to keep losing. For now, I’d recommend manually updating to ≥ v1.2.2-0.20230529154427-55a5a338d149 ; that should get us ~to the current Podman size; and getting all the way to A bit longer-term, per the conversation in sigstore/rekor#1511 , we might need to completely replace that dependency (containers/image#1845 ). And even longer-term, some protobuf dependencies might be imposed on us for compatibility with Cosign, making some parts of that size increase hard to avoid. |
Thanks for the details and additional context. |
For the record, I can’t find any code path that could trigger the vulnerable code. It’s included but dead. |
Closing in favor of #18833 |
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps github.com/sigstore/rekor from 1.1.2-0.20230508234306-ad288b385a44 to 1.2.0.
Changelog
Sourced from github.com/sigstore/rekor's changelog.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.