What is the CVSS score of CVE-2018-1002205?

CVE-2018-1002205 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N. EPSS exploitation probability: 10.4%.

Is there a patch available for CVE-2018-1002205?

Yes, a patch is available for CVE-2018-1002205. Update the affected software to the latest version immediately.

Dotnetzip Semverd CVE-2018-1002205

MEDIUM

Path Traversal (CWE-22)

2018-07-25 report@snyk.io

Path Traversal Dotnetzip Semverd

5.5

CVSS 3.1 · Vendor: snyk

Severity by source

Vendor (snyk) PRIMARY

5.5 MEDIUM

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

Primary rating from Vendor (snyk) · only source for this CVE.

CVSS VectorVendor: snyk

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

CVE Published

Jul 25, 2018 - 17:29 cve.org

MEDIUM 5.5

DescriptionCVE.org

AnalysisAI

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. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity. This Path Traversal vulnerability could allow attackers to access files and directories outside the intended path.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. 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'. Affected products include: Dotnetzip.Semverd Project Dotnetzip.Semverd. Version information: before 1.11.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.