CVE-2018-3824 (Medium) detected in elasticsearch-2.3.1.jar - autoclosed

[mend-for-github-com]

CVE-2018-3824 - Medium Severity Vulnerability

Vulnerable Library - elasticsearch-2.3.1.jar

Elasticsearch - Open Source, Distributed, RESTful Search Engine

Path to dependency file: Resiliency-Studio/resiliency-studio-service/pom.xml

Path to vulnerable library: ory/org/elasticsearch/elasticsearch/2.3.1/elasticsearch-2.3.1.jar

Dependency Hierarchy:

• ❌ elasticsearch-2.3.1.jar (Vulnerable Library)

Found in HEAD commit: 27f5ba6623ed8d6b149733f3ad245fc8133f1ffc

Found in base branch: master

Vulnerability Details

X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. If an attacker is able to inject data into an index that has a ML job running against it, then when another user views the results of the ML job it could allow the attacker to obtain sensitive information from or perform destructive actions on behalf of that other ML user.

Publish Date: 2018-09-19

URL: CVE-2018-3824

CVSS 3 Score Details (6.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3824

Release Date: 2018-09-19

Fix Resolution: org.elasticsearch:elasticsearch:5.6.9,org.elasticsearch:elasticsearch:6.2.4

---

⛑️ Automatic Remediation is available for this issue

[mend-for-github-com]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #70

[mend-for-github-com]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #70

[mend-for-github-com]

ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #70