LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1002205: DotNetZip.Semvered before 1.11.0 is vulnerable to directory traversal, allowing attackers to write to arbit...

DotNetZip.Semvered before 1.11.0 is vulnerable to directory traversal, allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction. This vulnerability is also known as 'Zip-Slip'.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE is a Zip-Slip flaw in DotNetZip.Semvered before 1.11.0. If a user or system extracts a malicious ZIP with the vulnerable library, files can be written outside the intended folder, potentially overwriting important application files.

Executive priority

Prioritize remediation for systems that accept external ZIP files or automate archive ingestion. This is not marked as actively exploited, but the business impact can be serious if file overwrite affects application integrity.

Technical view

The vulnerable extraction logic mishandles archive entry paths containing parent-directory traversal. The CVSS vector is local, low complexity, no privileges required, and user interaction required, with high integrity impact. Sources identify the issue as CWE-22 and a fix associated with version 1.11.0.

Likely exposure

Exposure is likely where .NET applications use DotNetZip.Semvered before 1.11.0 to extract ZIP files from users, partners, email, uploads, or automated import pipelines.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Abuse requires a crafted ZIP archive being extracted by a vulnerable application context.

Researcher notes

Focus validation on vulnerable dependency presence and archive extraction trust boundaries. The evidence supports arbitrary file write through directory traversal during extraction, but does not provide environment-specific exploitability or active exploitation evidence.

Mitigation direction

  • Upgrade DotNetZip.Semvered to version 1.11.0 or later.
  • Avoid extracting untrusted ZIP files with affected versions.
  • Run archive extraction with least privilege and isolated working directories.
  • Review vendor guidance and the linked fix before accepting compensating controls.

Validation and detection

  • Check dependency manifests and lock files for DotNetZip.Semvered versions before 1.11.0.
  • Identify application paths that extract ZIP files from untrusted sources.
  • Confirm deployed runtime packages match the fixed dependency version.
  • Review extraction code for canonical path checks before file writes.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1002205 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2018-1002205Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DotNetZipDotNetZip.SemveredunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.