-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[zlib] Fix CVE-2022-37434 #26792
[zlib] Fix CVE-2022-37434 #26792
Conversation
Hope this all works out (first time contributing), corresponding issue: #26790 |
Co-authored-by: Frank <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
PRs must add only one version and must not modify any published versions
When making any changes to a library, the version or port-version in vcpkg.json
or CONTROL
must be modified.
error: checked-in files for zlib have changed but the version was not updated
version: 1.2.12#2
old SHA: 026d6d9651ff45fd010acbc952c303d7069f2be8
new SHA: d40d86865ecbcc5b54d21f840dd2212556aeadd5
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@madler has done the new build, the 1.2.13 has been released with the CVE-2022-37434 fix. |
@Neustradamus You can submit a new issue to update |
Describe the pull request
What does your PR fix?
Fixes CVE-2022-37434 for zlib through 1.2.12
Which triplets are supported/not supported? Have you updated the [CI baseline]
Same as before
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?Yes