Skip to content

fix(docx): repair .docx zips with case-mismatched local headers (#1812)#1861

Open
haosenwang1018 wants to merge 1 commit into
microsoft:mainfrom
haosenwang1018:fix/1812-docx-zip-name-casing
Open

fix(docx): repair .docx zips with case-mismatched local headers (#1812)#1861
haosenwang1018 wants to merge 1 commit into
microsoft:mainfrom
haosenwang1018:fix/1812-docx-zip-name-casing

Conversation

@haosenwang1018
Copy link
Copy Markdown

Issue

Closes #1812

Root cause

Some .docx producers emit zip files where the local file header name and the central-directory name differ in case only (e.g. customXml/item2.xml centrally, customXML/item2.xml locally). Per APPNOTE the central directory is authoritative; most zip tools accept the mismatch but Python's zipfile strictly validates and raises BadZipFile mid-conversion. The user sees:

DocxConverter threw BadZipFile with message:
  File name in directory 'customXml/item2.xml' and header
  b'customXML/item2.xml' differ.

Fix

_fix_zip_name_casing scans local file headers, finds entries that match the central name when lower-cased and have the same byte length (always true for ASCII case-only mismatches), and rewrites the header bytes in-memory to match. Byte-length preserving → no offset recomputation needed. pre_process_docx calls it as the first step so every conversion path benefits.

If the central directory itself is unparseable we leave the input alone so the caller still sees the original error — no silent data loss.

This is the same approach the issue body proposed; the implementation hardens the matching predicate (added local.lower() == central.lower() so we only patch true case-only differences, not arbitrary same-length renames) and treats BadZipFile on the central directory as out-of-scope.

Tests

  • test_setup_actually_reproduces_badzipfile — guard that the test fixture really does trigger BadZipFile against unfixed zipfile. Without this, a future Python that loosens the validation would let the regression test below pass for the wrong reason.
  • test_fix_zip_name_casing_repairs_mismatched_local_header — the helper rewrites a deliberately mismatched archive into one that opens cleanly.
  • test_pre_process_docx_accepts_case_mismatched_archive — end-to-end: a mismatched .docx no longer crashes pre_process_docx and the post-processed archive still contains both the body and the originally-mismatched entry.
  • test_fix_zip_name_casing_passes_through_normal_archive — regression guard against unwanted rewrites of well-formed input.
$ pytest tests/test_docx_zip_case_mismatch.py tests/test_module_misc.py -k "docx or zip"
6 passed

…ory in case only

Closes microsoft#1812

Some .docx producers (notably certain legal-document systems and some
older Microsoft Word builds) emit zip files where the local file
header name and the central-directory name differ in case only — for
example, ``customXml/item2.xml`` in the central directory but
``customXML/item2.xml`` in the local file header.

Most zip tools accept this. Python's ``zipfile`` strictly validates
and raises ``BadZipFile`` mid-conversion, surfaced to the user as::

    DocxConverter threw BadZipFile with message:
      File name in directory 'customXml/item2.xml' and header
      b'customXML/item2.xml' differ.

Per APPNOTE the central directory is authoritative. Add
``_fix_zip_name_casing`` that scans local file headers, finds entries
that match the central name when lower-cased and have the same byte
length (always true for ASCII case-only mismatches), and rewrites the
header bytes in-memory to match. The patch is byte-length preserving,
so no offset recomputation is needed. Call this from the start of
``pre_process_docx`` so every code path that runs through it benefits.

If the central directory itself is unparseable we leave the stream
alone so the caller surfaces the same error the unfixed code would
have — no silent data loss.

Tests:

- ``test_setup_actually_reproduces_badzipfile`` is a guard that the
  test fixture really does trip ``BadZipFile``; if Python ever stops
  validating local-vs-central name parity, the regression below would
  pass for the wrong reason.
- ``test_fix_zip_name_casing_repairs_mismatched_local_header`` and
  ``test_pre_process_docx_accepts_case_mismatched_archive`` cover the
  fix directly.
- ``test_fix_zip_name_casing_passes_through_normal_archive`` is a
  regression guard against rewriting well-formed inputs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@microsoft-github-policy-service
Copy link
Copy Markdown

@haosenwang1018 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BadZipFile crash on .docx files with case-mismatched zip entry names

1 participant