You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Concatenating two valid ZIP files produces a blob where different parsers focus on different EOCD records. Many tools locate the last End Of Central Directory (EOCD), while some libraries (e.g., ZipArchive in specific workflows) may parse the first archive they find. If validation enumerates the first archive and extraction uses another tool that honors the last EOCD, a benign archive can pass checks while a malicious one gets extracted.
- If the server validates with one parser (sees benign.zip) but extracts with another (processes evil.zip), the blocked file lands in the extraction path.
462
452
463
-
Mitigations
464
-
- Reject archives with trailing bytes or multiple EOCDs; verify exactly one well‑formed archive.
465
-
- Use the same parser for validation and extraction.
466
-
- Disallow server‑side extraction to web‑served, executable folders; prefer offline processing with strict allowlists.
467
-
468
453
## ImageTragic
469
454
470
455
Upload this content with an image extension to exploit the vulnerability **(ImageMagick , 7.0.1-1)** (form the [exploit](https://www.exploit-db.com/exploits/39767))
@@ -522,4 +507,4 @@ How to avoid file type detections by uploading a valid JSON file even if not all
0 commit comments