Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Directory Traversal in DotNetZip ZipEntry extraction

IdentifiersCVE-2024-48510CWE-22· Improper Limitation of a Pathname…

CVE-2024-48510 is a directory traversal vulnerability in DotNetZip 1.16.0 and earlier, affecting ZIP extraction logic in src/Zip.Shared/ZipEntry.Extract.cs. A crafted ZIP archive can contain entry names that traverse outside the intended extraction directory. When a victim opens or extracts a malicious archive with an affected version, the library may write attacker-controlled files to arbitrary filesystem locations instead of constraining output to the target extraction path. Because this can place files in executable or otherwise security-sensitive locations, the issue can be leveraged for arbitrary code execution. The available reporting notes that exploitation requires a victim to open a malicious file and that the vulnerable product line is no longer supported by the maintainer.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to escape the intended extraction directory and write files to arbitrary paths on the target system. Depending on where files can be written and how the host application or operating system subsequently processes them, this can result in arbitrary code execution. At minimum, the vulnerability enables unauthorized file overwrite and integrity compromise; in favorable conditions for the attacker, it can lead to full compromise of the affected application context.

Mitigation

If you can’t patch tonight, do this now.

Do not extract untrusted ZIP archives with affected DotNetZip/ProDotNetZip versions. Implement strict validation and canonicalization of archive entry paths before extraction, rejecting absolute paths, drive letters, UNC paths, and any traversal sequences such as '..' after normalization. Enforce extraction into a dedicated locked-down directory with minimal privileges and prevent overwriting of sensitive files. Where possible, sandbox archive processing and restrict write permissions so that even a successful traversal cannot place files into executable or startup locations.

Remediation

Patch, then assume compromise.

Upgrade to a fixed release. The provided advisory indicates ProDotNetZip should be upgraded to 1.19.0 or later. For DotNetZip, upgrade from 1.16.0 or earlier to a newer version that includes the fix; however, the content also notes the affected DotNetZip product line is no longer supported by the maintainer, so migration to a maintained fixed fork or replacement library may be necessary. For downstream products embedding the vulnerable library, apply the vendor-provided update, such as Rockwell AADvance-Trusted SIS Workstation 2.01.00 or later where applicable.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Dotnetzip.Semverd ProjectDotnetzip.Semverdapplication
MihulaProdotnetzipapplication
NuGetDotnetzipapplication
Rockwell AutomationAadvance - Trusted Sis Workstationapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.