dicomlock 0.7.0__tar.gz

dicomlock-0.7.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, 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
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Vijay Thakore
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dicomlock-0.7.0/PKG-INFO

@@ -0,0 +1,136 @@
+Metadata-Version: 2.4
+Name: dicomlock
+Version: 0.7.0
+Summary: Open-source, self-hosted DICOM file-security scanner + Content Disarm & Reconstruction (CDR)
+Author: Vijay Thakore
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://dicomlock.com
+Project-URL: Repository, https://github.com/vthakore23/dicomlock
+Project-URL: Issues, https://github.com/vthakore23/dicomlock/issues
+Keywords: dicom,security,cdr,content-disarm,medical-imaging,pacs,polyglot
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Healthcare Industry
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Security
+Classifier: Topic :: Scientific/Engineering :: Medical Science Apps.
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydicom>=2.4.0
+Requires-Dist: numpy>=1.24.0
+Requires-Dist: python-gdcm>=3.0.0
+Requires-Dist: pylibjpeg>=2.0.0
+Requires-Dist: pylibjpeg-libjpeg>=2.0.0
+Requires-Dist: pylibjpeg-openjpeg>=2.0.0
+Provides-Extra: server
+Requires-Dist: fastapi>=0.110.0; extra == "server"
+Requires-Dist: uvicorn>=0.29.0; extra == "server"
+Requires-Dist: python-multipart>=0.0.9; extra == "server"
+Provides-Extra: full
+Requires-Dist: scipy>=1.11.0; extra == "full"
+Requires-Dist: scikit-image>=0.21.0; extra == "full"
+Requires-Dist: Pillow>=10.0.0; extra == "full"
+Requires-Dist: PyWavelets>=1.4.0; extra == "full"
+Dynamic: license-file
+
+# DicomLock
+
+Open-source, self-hosted security for DICOM medical-image files. It scans a file for the ways it can be weaponized, then disarms it by rebuilding a clean, clinically identical copy.
+
+[![PyPI](https://img.shields.io/pypi/v/dicomlock.svg)](https://pypi.org/project/dicomlock/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+A DICOM file is not just a picture. It is input for a parser, and hospital software has to read and decode all of it before anyone sees an image. That step is the attack surface. DicomLock checks the file for polyglot malware, parser-exploit constructions, and pixel data that routes through vulnerable image or video codecs, then rebuilds a clean version before the file reaches a PACS, viewer, or model. It runs inside your network, so no patient data leaves the building.
+
+This is Content Disarm and Reconstruction (CDR) for DICOM, built to be open and auditable.
+
+## Install
+
+```bash
+pip install dicomlock
+```
+
+The core install pulls in the decoder backends (gdcm and pylibjpeg) so disarm works out of the box. Two optional extras:
+
+```bash
+pip install "dicomlock[server]"   # web UI and REST API
+pip install "dicomlock[full]"     # PHI / de-identification audit and legacy forensics
+```
+
+Python 3.10 or newer.
+
+## Usage
+
+```bash
+dicomlock file.dcm                 # scan one file
+dicomlock folder/                  # scan every .dcm in a folder
+dicomlock folder/ --disarm         # scan, then disarm or quarantine each file
+dicomlock file.dcm --deid          # add the PHI / de-identification audit
+```
+
+As a library:
+
+```python
+from scanner.pipeline import run_security_scan, disarm_or_quarantine, is_dangerous
+
+report = run_security_scan("file.dcm")
+if is_dangerous(report):
+    result = disarm_or_quarantine("file.dcm")   # {"action": "disarmed" | "quarantined", ...}
+```
+
+Web UI and API:
+
+```bash
+python server.py    # http://localhost:8899
+```
+
+Uploads are scanned in a temp directory and deleted right after, so PHI is never persisted.
+
+## How it works
+
+1. **Scan.** Deterministic, rule-based checks, no ML: preamble and polyglot signatures, length amplification, sequence-nesting depth, pixel-dimension and decompression bombs, private-tag payloads, codec-CVE exposure, and metadata integrity.
+2. **Disarm.** For files that are dangerous but recoverable, it zeroes the preamble, transcodes compressed pixels to native off the vulnerable codec (in a sandboxed subprocess), and filters private tags against a vendor allowlist. Lossless sources come out bit-exact. Lossy sources are decoded once with no new compression.
+3. **Quarantine.** Anything it cannot safely rebuild, such as length bombs and files no backend can decode, is held back. It re-scans its own output, so it never emits a file that still fails a check.
+
+The point of CDR is that it rebuilds from a validated canonical form instead of matching a known signature, so it neutralizes attacks it has never seen. That is the defense that holds up when vulnerabilities turn up faster than anyone can patch them, which is the situation for the systems a patch cycle reaches slowly: legacy and embedded medical devices, and software locked behind FDA recertification.
+
+## Why this is a real problem
+
+The 128-byte preamble can hold an executable header, so one file can be a valid scan and working malware at the same time (CVE-2019-11687, extended to Linux devices by ELFDICOM). Attacker-controlled length fields turn a 140-byte file into a multi-gigabyte allocation request. Encapsulated pixel and video data decodes through libjpeg, OpenJPEG, CharLS, and FFmpeg-class libraries that carry long CVE histories. Live examples in clinical software include the Orthanc auth bypass (CVE-2025-0896, CVSS 9.8) and MicroDicom remote code execution (CVE-2025-5943).
+
+DicomLock works on the file. It does not break or weaken encryption and makes no claim to.
+
+## Results
+
+All reproducible from the scripts in [`_attack_test/`](_attack_test/):
+
+- Zero false positives across 575 real clinical CT files, and zero on a separate mixed-compression corpus spanning 12 transfer syntaxes.
+- 20 of 20 crafted attack fixtures flagged by the expected check.
+- pydicom, GDCM, and dcmtk accept the weaponized files without complaint; DicomLock flags every one.
+- Disarmed pixels are bit-exact against two independent decoders (GDCM and pylibjpeg) on every lossless sample.
+- The codec decode is sandboxed, so a crashing or hanging decoder is contained and the file is quarantined, not the tool.
+
+The attack fixtures in this repo are inert. Polyglots carry only magic bytes, and payload tags carry a header plus zero padding. No working malware ships here.
+
+## Where it fits
+
+Commercial DICOM CDR already exists (OPSWAT, Votiro), and there is academic prior art, so "nobody does this" is not the pitch. DicomLock's reason to exist is that it is open, self-hosted, auditable, and PACS-depth. The transcoding, the vendor allowlist, and the parser-bomb rejection are all readable in source and run inside your network. The natural first users are research-imaging and data-engineering teams that already ingest untrusted external DICOM.
+
+It is a security and sanitization tool, not a medical device. It carries no diagnostic claim and no FDA clearance. See [THREAT_MODEL.md](THREAT_MODEL.md) for what it does and does not defend.
+
+## Documentation
+
+- [THREAT_MODEL.md](THREAT_MODEL.md), attacks defended and explicit non-claims
+- [ARCHITECTURE.md](ARCHITECTURE.md), module specs
+- [CONTRIBUTING.md](CONTRIBUTING.md), how to help with the CVE map, vendor allowlist, and codecs
+- [SECURITY.md](SECURITY.md), vulnerability disclosure
+
+## License
+
+[Apache-2.0](LICENSE), © 2026 Vijay Thakore. Provided as is, without warranty. DicomLock is a sanitization tool, not a medical device, and makes no diagnostic claim. Validate disarmed files in your own environment before any clinical use, and run on de-identified data where you can.

dicomlock-0.7.0/README.md

@@ -0,0 +1,96 @@
+# DicomLock
+
+Open-source, self-hosted security for DICOM medical-image files. It scans a file for the ways it can be weaponized, then disarms it by rebuilding a clean, clinically identical copy.
+
+[![PyPI](https://img.shields.io/pypi/v/dicomlock.svg)](https://pypi.org/project/dicomlock/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+A DICOM file is not just a picture. It is input for a parser, and hospital software has to read and decode all of it before anyone sees an image. That step is the attack surface. DicomLock checks the file for polyglot malware, parser-exploit constructions, and pixel data that routes through vulnerable image or video codecs, then rebuilds a clean version before the file reaches a PACS, viewer, or model. It runs inside your network, so no patient data leaves the building.
+
+This is Content Disarm and Reconstruction (CDR) for DICOM, built to be open and auditable.
+
+## Install
+
+```bash
+pip install dicomlock
+```
+
+The core install pulls in the decoder backends (gdcm and pylibjpeg) so disarm works out of the box. Two optional extras:
+
+```bash
+pip install "dicomlock[server]"   # web UI and REST API
+pip install "dicomlock[full]"     # PHI / de-identification audit and legacy forensics
+```
+
+Python 3.10 or newer.
+
+## Usage
+
+```bash
+dicomlock file.dcm                 # scan one file
+dicomlock folder/                  # scan every .dcm in a folder
+dicomlock folder/ --disarm         # scan, then disarm or quarantine each file
+dicomlock file.dcm --deid          # add the PHI / de-identification audit
+```
+
+As a library:
+
+```python
+from scanner.pipeline import run_security_scan, disarm_or_quarantine, is_dangerous
+
+report = run_security_scan("file.dcm")
+if is_dangerous(report):
+    result = disarm_or_quarantine("file.dcm")   # {"action": "disarmed" | "quarantined", ...}
+```
+
+Web UI and API:
+
+```bash
+python server.py    # http://localhost:8899
+```
+
+Uploads are scanned in a temp directory and deleted right after, so PHI is never persisted.
+
+## How it works
+
+1. **Scan.** Deterministic, rule-based checks, no ML: preamble and polyglot signatures, length amplification, sequence-nesting depth, pixel-dimension and decompression bombs, private-tag payloads, codec-CVE exposure, and metadata integrity.
+2. **Disarm.** For files that are dangerous but recoverable, it zeroes the preamble, transcodes compressed pixels to native off the vulnerable codec (in a sandboxed subprocess), and filters private tags against a vendor allowlist. Lossless sources come out bit-exact. Lossy sources are decoded once with no new compression.
+3. **Quarantine.** Anything it cannot safely rebuild, such as length bombs and files no backend can decode, is held back. It re-scans its own output, so it never emits a file that still fails a check.
+
+The point of CDR is that it rebuilds from a validated canonical form instead of matching a known signature, so it neutralizes attacks it has never seen. That is the defense that holds up when vulnerabilities turn up faster than anyone can patch them, which is the situation for the systems a patch cycle reaches slowly: legacy and embedded medical devices, and software locked behind FDA recertification.
+
+## Why this is a real problem
+
+The 128-byte preamble can hold an executable header, so one file can be a valid scan and working malware at the same time (CVE-2019-11687, extended to Linux devices by ELFDICOM). Attacker-controlled length fields turn a 140-byte file into a multi-gigabyte allocation request. Encapsulated pixel and video data decodes through libjpeg, OpenJPEG, CharLS, and FFmpeg-class libraries that carry long CVE histories. Live examples in clinical software include the Orthanc auth bypass (CVE-2025-0896, CVSS 9.8) and MicroDicom remote code execution (CVE-2025-5943).
+
+DicomLock works on the file. It does not break or weaken encryption and makes no claim to.
+
+## Results
+
+All reproducible from the scripts in [`_attack_test/`](_attack_test/):
+
+- Zero false positives across 575 real clinical CT files, and zero on a separate mixed-compression corpus spanning 12 transfer syntaxes.
+- 20 of 20 crafted attack fixtures flagged by the expected check.
+- pydicom, GDCM, and dcmtk accept the weaponized files without complaint; DicomLock flags every one.
+- Disarmed pixels are bit-exact against two independent decoders (GDCM and pylibjpeg) on every lossless sample.
+- The codec decode is sandboxed, so a crashing or hanging decoder is contained and the file is quarantined, not the tool.
+
+The attack fixtures in this repo are inert. Polyglots carry only magic bytes, and payload tags carry a header plus zero padding. No working malware ships here.
+
+## Where it fits
+
+Commercial DICOM CDR already exists (OPSWAT, Votiro), and there is academic prior art, so "nobody does this" is not the pitch. DicomLock's reason to exist is that it is open, self-hosted, auditable, and PACS-depth. The transcoding, the vendor allowlist, and the parser-bomb rejection are all readable in source and run inside your network. The natural first users are research-imaging and data-engineering teams that already ingest untrusted external DICOM.
+
+It is a security and sanitization tool, not a medical device. It carries no diagnostic claim and no FDA clearance. See [THREAT_MODEL.md](THREAT_MODEL.md) for what it does and does not defend.
+
+## Documentation
+
+- [THREAT_MODEL.md](THREAT_MODEL.md), attacks defended and explicit non-claims
+- [ARCHITECTURE.md](ARCHITECTURE.md), module specs
+- [CONTRIBUTING.md](CONTRIBUTING.md), how to help with the CVE map, vendor allowlist, and codecs
+- [SECURITY.md](SECURITY.md), vulnerability disclosure
+
+## License
+
+[Apache-2.0](LICENSE), © 2026 Vijay Thakore. Provided as is, without warranty. DicomLock is a sanitization tool, not a medical device, and makes no diagnostic claim. Validate disarmed files in your own environment before any clinical use, and run on de-identified data where you can.

dicomlock-0.7.0/dicomlock.egg-info/PKG-INFO

@@ -0,0 +1,136 @@
+Metadata-Version: 2.4
+Name: dicomlock
+Version: 0.7.0
+Summary: Open-source, self-hosted DICOM file-security scanner + Content Disarm & Reconstruction (CDR)
+Author: Vijay Thakore
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://dicomlock.com
+Project-URL: Repository, https://github.com/vthakore23/dicomlock
+Project-URL: Issues, https://github.com/vthakore23/dicomlock/issues
+Keywords: dicom,security,cdr,content-disarm,medical-imaging,pacs,polyglot
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Healthcare Industry
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Security
+Classifier: Topic :: Scientific/Engineering :: Medical Science Apps.
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydicom>=2.4.0
+Requires-Dist: numpy>=1.24.0
+Requires-Dist: python-gdcm>=3.0.0
+Requires-Dist: pylibjpeg>=2.0.0
+Requires-Dist: pylibjpeg-libjpeg>=2.0.0
+Requires-Dist: pylibjpeg-openjpeg>=2.0.0
+Provides-Extra: server
+Requires-Dist: fastapi>=0.110.0; extra == "server"
+Requires-Dist: uvicorn>=0.29.0; extra == "server"
+Requires-Dist: python-multipart>=0.0.9; extra == "server"
+Provides-Extra: full
+Requires-Dist: scipy>=1.11.0; extra == "full"
+Requires-Dist: scikit-image>=0.21.0; extra == "full"
+Requires-Dist: Pillow>=10.0.0; extra == "full"
+Requires-Dist: PyWavelets>=1.4.0; extra == "full"
+Dynamic: license-file
+
+# DicomLock
+
+Open-source, self-hosted security for DICOM medical-image files. It scans a file for the ways it can be weaponized, then disarms it by rebuilding a clean, clinically identical copy.
+
+[![PyPI](https://img.shields.io/pypi/v/dicomlock.svg)](https://pypi.org/project/dicomlock/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+A DICOM file is not just a picture. It is input for a parser, and hospital software has to read and decode all of it before anyone sees an image. That step is the attack surface. DicomLock checks the file for polyglot malware, parser-exploit constructions, and pixel data that routes through vulnerable image or video codecs, then rebuilds a clean version before the file reaches a PACS, viewer, or model. It runs inside your network, so no patient data leaves the building.
+
+This is Content Disarm and Reconstruction (CDR) for DICOM, built to be open and auditable.
+
+## Install
+
+```bash
+pip install dicomlock
+```
+
+The core install pulls in the decoder backends (gdcm and pylibjpeg) so disarm works out of the box. Two optional extras:
+
+```bash
+pip install "dicomlock[server]"   # web UI and REST API
+pip install "dicomlock[full]"     # PHI / de-identification audit and legacy forensics
+```
+
+Python 3.10 or newer.
+
+## Usage
+
+```bash
+dicomlock file.dcm                 # scan one file
+dicomlock folder/                  # scan every .dcm in a folder
+dicomlock folder/ --disarm         # scan, then disarm or quarantine each file
+dicomlock file.dcm --deid          # add the PHI / de-identification audit
+```
+
+As a library:
+
+```python
+from scanner.pipeline import run_security_scan, disarm_or_quarantine, is_dangerous
+
+report = run_security_scan("file.dcm")
+if is_dangerous(report):
+    result = disarm_or_quarantine("file.dcm")   # {"action": "disarmed" | "quarantined", ...}
+```
+
+Web UI and API:
+
+```bash
+python server.py    # http://localhost:8899
+```
+
+Uploads are scanned in a temp directory and deleted right after, so PHI is never persisted.
+
+## How it works
+
+1. **Scan.** Deterministic, rule-based checks, no ML: preamble and polyglot signatures, length amplification, sequence-nesting depth, pixel-dimension and decompression bombs, private-tag payloads, codec-CVE exposure, and metadata integrity.
+2. **Disarm.** For files that are dangerous but recoverable, it zeroes the preamble, transcodes compressed pixels to native off the vulnerable codec (in a sandboxed subprocess), and filters private tags against a vendor allowlist. Lossless sources come out bit-exact. Lossy sources are decoded once with no new compression.
+3. **Quarantine.** Anything it cannot safely rebuild, such as length bombs and files no backend can decode, is held back. It re-scans its own output, so it never emits a file that still fails a check.
+
+The point of CDR is that it rebuilds from a validated canonical form instead of matching a known signature, so it neutralizes attacks it has never seen. That is the defense that holds up when vulnerabilities turn up faster than anyone can patch them, which is the situation for the systems a patch cycle reaches slowly: legacy and embedded medical devices, and software locked behind FDA recertification.
+
+## Why this is a real problem
+
+The 128-byte preamble can hold an executable header, so one file can be a valid scan and working malware at the same time (CVE-2019-11687, extended to Linux devices by ELFDICOM). Attacker-controlled length fields turn a 140-byte file into a multi-gigabyte allocation request. Encapsulated pixel and video data decodes through libjpeg, OpenJPEG, CharLS, and FFmpeg-class libraries that carry long CVE histories. Live examples in clinical software include the Orthanc auth bypass (CVE-2025-0896, CVSS 9.8) and MicroDicom remote code execution (CVE-2025-5943).
+
+DicomLock works on the file. It does not break or weaken encryption and makes no claim to.
+
+## Results
+
+All reproducible from the scripts in [`_attack_test/`](_attack_test/):
+
+- Zero false positives across 575 real clinical CT files, and zero on a separate mixed-compression corpus spanning 12 transfer syntaxes.
+- 20 of 20 crafted attack fixtures flagged by the expected check.
+- pydicom, GDCM, and dcmtk accept the weaponized files without complaint; DicomLock flags every one.
+- Disarmed pixels are bit-exact against two independent decoders (GDCM and pylibjpeg) on every lossless sample.
+- The codec decode is sandboxed, so a crashing or hanging decoder is contained and the file is quarantined, not the tool.
+
+The attack fixtures in this repo are inert. Polyglots carry only magic bytes, and payload tags carry a header plus zero padding. No working malware ships here.
+
+## Where it fits
+
+Commercial DICOM CDR already exists (OPSWAT, Votiro), and there is academic prior art, so "nobody does this" is not the pitch. DicomLock's reason to exist is that it is open, self-hosted, auditable, and PACS-depth. The transcoding, the vendor allowlist, and the parser-bomb rejection are all readable in source and run inside your network. The natural first users are research-imaging and data-engineering teams that already ingest untrusted external DICOM.
+
+It is a security and sanitization tool, not a medical device. It carries no diagnostic claim and no FDA clearance. See [THREAT_MODEL.md](THREAT_MODEL.md) for what it does and does not defend.
+
+## Documentation
+
+- [THREAT_MODEL.md](THREAT_MODEL.md), attacks defended and explicit non-claims
+- [ARCHITECTURE.md](ARCHITECTURE.md), module specs
+- [CONTRIBUTING.md](CONTRIBUTING.md), how to help with the CVE map, vendor allowlist, and codecs
+- [SECURITY.md](SECURITY.md), vulnerability disclosure
+
+## License
+
+[Apache-2.0](LICENSE), © 2026 Vijay Thakore. Provided as is, without warranty. DicomLock is a sanitization tool, not a medical device, and makes no diagnostic claim. Validate disarmed files in your own environment before any clinical use, and run on de-identified data where you can.

dicomlock-0.7.0/dicomlock.egg-info/SOURCES.txt

@@ -0,0 +1,27 @@
+LICENSE
+README.md
+pyproject.toml
+dicomlock.egg-info/PKG-INFO
+dicomlock.egg-info/SOURCES.txt
+dicomlock.egg-info/dependency_links.txt
+dicomlock.egg-info/entry_points.txt
+dicomlock.egg-info/requires.txt
+dicomlock.egg-info/top_level.txt
+scanner/__init__.py
+scanner/_resources.py
+scanner/_sandbox.py
+scanner/calibration.py
+scanner/classify.py
+scanner/cli.py
+scanner/codec_cve.py
+scanner/deid_auditor.py
+scanner/disarm.py
+scanner/file_security.py
+scanner/findings.py
+scanner/ingest.py
+scanner/metadata.py
+scanner/pipeline.py
+scanner/pixel_advanced.py
+scanner/pixel_analysis.py
+scanner/data/dicom_codec_cve.json
+scanner/data/vendor_private_tags.json

dicomlock-0.7.0/dicomlock.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

dicomlock-0.7.0/dicomlock.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+dicomlock = scanner.cli:main

dicomlock-0.7.0/dicomlock.egg-info/requires.txt

@@ -0,0 +1,17 @@
+pydicom>=2.4.0
+numpy>=1.24.0
+python-gdcm>=3.0.0
+pylibjpeg>=2.0.0
+pylibjpeg-libjpeg>=2.0.0
+pylibjpeg-openjpeg>=2.0.0
+
+[full]
+scipy>=1.11.0
+scikit-image>=0.21.0
+Pillow>=10.0.0
+PyWavelets>=1.4.0
+
+[server]
+fastapi>=0.110.0
+uvicorn>=0.29.0
+python-multipart>=0.0.9

dicomlock-0.7.0/dicomlock.egg-info/top_level.txt

@@ -0,0 +1 @@
+scanner