cve.bz

CVE-2024-48510 Path traversal

9.8 criticalEPSS 2.0%Fix available

Critical (9.8). EPSS 2.0% estimated probability of exploitation activity in the next 30 days. Fixed in ProDotNetZip 1.19.0.

On this page
Directory Traversal vulnerability in DotNetZip v.1.16.0 and before allows a remote attacker to execute arbitrary code via the src/Zip.Shared/ZipEntry.Extract.cs component NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.0% (unchanged from 2.0% a week ago; 2.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2024-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-48510 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-48510?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-48510?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-48510 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
mihula:prodotnetzipbefore 1.19.0
dotnetzip.semverd_project:dotnetzip.semverdfrom 1.10.1 through 1.16.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xhg6-9j5j-w4vfNuGetDotNetZip>=1.10.1 <=1.16.0no fix published
GHSA-xhg6-9j5j-w4vfNuGetProDotNetZip<1.19.01.19.0

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-25-317-10*Rockwell Automation AADvance-Trusted SIS Workstation *2025-11-13Critical ManufacturingRockwell Automation AADvance-Trusted SIS Workstation: >=2.00.00|<2.00.04none listed
ICSA-25-051-04Siemens SiPass Integrated2025-02-17Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSiPass integrated V2.90, SiPass integrated V2.95none listed
ICSA-25-037-03ABB Drive Composer2025-01-10Critical ManufacturingDrive Composer entry <= 2.9.0.1, Drive Composer pro <= 2.9.0.1Drive Composer entry 2.9.1, Drive Composer pro 2.9.1

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON