CVE-2020-10683 (Critical) detected in dom4j-1.1.jar

[mend-for-github-com]

CVE-2020-10683 - Critical Severity Vulnerability

Vulnerable Library - dom4j-1.1.jar

Path to dependency file: /plugins/sitemesh/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar,/home/wss-scanner/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar

Dependency Hierarchy:

• velocity-tools-2.0.jar (Root Library)
  • ❌ dom4j-1.1.jar (Vulnerable Library)

Found in HEAD commit: 6950763af860884188f4080d19a18c5ede16cd74

Found in base branch: master

Vulnerability Details

dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.

Publish Date: 2020-05-01

URL: CVE-2020-10683

CVSS 3 Score Details (9.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2020-05-01

Fix Resolution: org.dom4j:dom4j:2.1.3,org.dom4j:dom4j:2.0.3