CVE-2023-45853: MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewF...
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.
Security readout for executives and security teams
Plain-English summary
This flaw affects MiniZip ZIP-creation code, not core supported zlib. If an application creates ZIP files using attacker-controlled long names, comments, or extra fields, memory corruption may result. Public sources also identify pyminizip through 0.2.6 as vulnerable because it bundles affected code.
Executive priority
Treat as high priority for products or internal services that generate ZIP files from untrusted content. It is lower urgency for systems only using supported core zlib compression and not MiniZip, but embedded copies can be easy to miss.
Technical view
CVE-2023-45853 is an integer overflow in MiniZip through zlib 1.3, leading to heap-based buffer overflow in zipOpenNewFileInZip4_64 when handling long filename, comment, or extra field values. The CVSS 3.1 score is 8.8 with low complexity, no privileges, and user interaction required.
Likely exposure
Exposure is most likely in software that embeds zlib contrib MiniZip, installs distro minizip packages, or uses pyminizip through 0.2.6. Standard zlib use without MiniZip is not shown as affected in the supplied sources.
Exploitation context
The supplied bundle does not show CISA KEV listing or active exploitation evidence. Practical risk depends on whether attackers can influence ZIP entry metadata passed into vulnerable ZIP-creation routines, directly or through an upload, export, packaging, or automation workflow.
Researcher notes
The key distinction is product boundary: sources state MiniZip is not a supported part of zlib, yet downstream projects bundle or expose it. Focus analysis on call paths into zipOpenNewFileInZip4_64 and downstream vendored code, not generic zlib presence alone.
Mitigation direction
Apply vendor or distribution minizip updates where available.
Inventory embedded MiniZip copies and replace affected source with maintained vendor guidance.
Avoid pyminizip through 0.2.6 where attacker-controlled input reaches compression.
Check Siemens, NetApp, Debian, Gentoo, Chromium, and upstream guidance for product-specific status.
Reduce exposure by rejecting unusually long ZIP names, comments, and extra fields before compression.
Validation and detection
Search dependency manifests and SBOMs for minizip, zlib contrib MiniZip, and pyminizip.
Confirm whether ZIP creation accepts user-controlled filenames, comments, or extra fields.
Verify deployed package versions against Debian, Gentoo, and vendor advisories.
Review embedded third-party source trees for contrib/minizip code copies.
Document unaffected systems where MiniZip ZIP creation is absent.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
3ADP providers
13Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.