Skip to content
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

frp/0.61.1-r0: cve remediation #37922

Merged
merged 1 commit into from
Dec 24, 2024
Merged

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 20, 2024

@octo-sts octo-sts bot added automated pr GHSA-w32m-9786-jp63 go/bump request-cve-remediation frp/0.61.1-r0 bincapz/blocking Bincapz (aka malcontent) scan results detected CRITICALs on the packages. labels Dec 20, 2024
@ajayk
Copy link
Member

ajayk commented Dec 24, 2024

Frp is a proxy bincapz classification seems correct no other changes from the last build

@ajayk ajayk enabled auto-merge (squash) December 24, 2024 17:58
@ajayk ajayk merged commit ab68826 into main Dec 24, 2024
14 of 15 checks passed
@ajayk ajayk deleted the cve-frp-8de313b0cfe68a1c4b166e078b13f134 branch December 24, 2024 17:58
@egibs
Copy link
Member

egibs commented Dec 24, 2024

Frp is a proxy bincapz classification seems correct no other changes from the last build

Yep, we expect FRP to trigger a critical.

@egibs egibs added the malcontent/reviewed The malcontent findings in this PR have been manually reviewed by security. label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/blocking Bincapz (aka malcontent) scan results detected CRITICALs on the packages. frp/0.61.1-r0 GHSA-w32m-9786-jp63 go/bump malcontent/reviewed The malcontent findings in this PR have been manually reviewed by security. request-cve-remediation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants