Loading vulnerability…
CVE-2023-41717 is an inappropriate file type control vulnerability in Zscaler Proxy versions 3.6.1.25 and earlier. A local attacker can bypass restrictions governing file downloads and uploads.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository demonstrates a proof-of-concept exploit for CVE-2023-41717, a vulnerability in Zscaler Proxy (versions 3.6.1.25 and prior) that allows local attackers to bypass file type restrictions on password-protected archive downloads. The repository contains a detailed README.md explaining two exploitation methods: (1) manually crafting HTTP range requests to download file fragments and (2) using the BITS protocol via bitsadmin.exe to split downloads into chunks. The included PowerShell script (Reconstruct-Payload.ps1) reconstructs the original file from base64-encoded fragments obtained from HTTP 206 Partial Content responses. The exploit targets Windows environments with Zscaler Proxy deployed and demonstrates that file type controls can be bypassed by reconstructing files from multiple allowed fragments. The repository is structured with a single exploit script and comprehensive documentation, serving as a clear proof-of-concept for the described vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.