-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Upgrade to zlib v1.2.12 in CPython binary releases #91350
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
Comments
zlib v1.2.11 as used in Windows binary releases contains a security issue that, while fixed in its git repo years ago, never wound up in a release or a CVE until just now. Folllow the https://www.openwall.com/lists/oss-security/2022/03/24/1 thread and the and recently assigned CVE-2018-25032. I believe we only ship our own zlib on Windows so this issue is tagged as such. The above oss-security thread is where an idea of severity will come out. |
New changeset 6066739 by Zachary Ware in branch 'main': |
New changeset 0f0f85e by Miss Islington (bot) in branch '3.9': |
New changeset 16a809f by Miss Islington (bot) in branch '3.10': |
Is there anything left to do in this issue? Can we close it? |
It seems like zlib is still outdated in Python 3.8. I have a tool to check for "external libraries versions": https://github.com/vstinner/misc/blob/main/cpython/external_versions.py
|
yep just waiting on that 3.8 PR being merged by its RM. we don't have a good way to indicate which branches an issue remains a release-blocker for. |
With the merge of #32250, this is now resolved in all active branches. Does anyone have a handle on whether the severity of the CVE is high enough to warrant releases? |
Since we only ship our own zlib with installers and 3.7-3.8 aren't shipping installers anymore, I don't think we need a security release for that. The only other change in 3.8 is a sqlite segfault fix so I think I'll pass on releasing a 3.8 at this time. |
Likewise with 3.7 so time to close this. Thanks, everyone! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: