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

CVE-2018-12036 has a CVSS 3.0 base score of 7.8 (High). CVSS vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.7%.

Is there a public PoC exploit available for CVE-2018-12036?

Yes, a public proof-of-concept exploit is available for CVE-2018-12036. Prioritise patching immediately. EPSS: 1.7%.

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

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

Dependency Check CVE-2018-12036

HIGH

Path Traversal (CWE-22)

2018-06-07 cve@mitre.org

Path Traversal Dependency Check

7.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jun 07, 2018 - 18:29 nvd

HIGH 7.8

DescriptionNVD

OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames.

AnalysisAI

OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames. Affected products include: Owasp Dependency-Check. Version information: before 3.2.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.