PYMINIZIP · CVE-2023-45853 · Package
FIX → 1.3.1
pyminizip bundles MiniZip code from zlib 1.2.11, which has an integer overflow in zipOpenNewFileInZip4_64 when a file name, comment, or extra field is very long. The overflow leads to a heap-based buffer overflow that can crash or potentially run attacker-supplied code.
first public Oct 14, 2023 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any application that uses pyminizip 0.2.6 or older to create zip archives, especially where file names, comments, or extra fields come from untrusted input. Code that does not use pyminizip, or only processes archives it created itself from trusted data, is much less exposed. The sources do not say which zlib versions beyond 1.3 are affected.
Not affected if not-using-pyminizip, untrusted-input
Who cares pyminizip, python
pip show pyminizip to see the installed version, and check whether it is 0.2.6 or older.Upgrade to 1.3.1
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.