vue-2.5.16.tgz: 1 vulnerabilities (highest severity is: 6.1)

[mend-for-github-com]

Vulnerable Library - vue-2.5.16.tgz

Reactive, component-oriented view layer for modern web interfaces.

Library home page: https://registry.npmjs.org/vue/-/vue-2.5.16.tgz

Path to dependency file: /applications/gui/package.json

Path to vulnerable library: /applications/gui/node_modules/vue/package.json

Found in HEAD commit: 4e5656db54be4b22481fe3774c2caeba51bac190

Vulnerabilities

CVE	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (vue version)	Remediation Possible**	Reachability
WS-2018-0162	Medium	6.1	Not Defined		vue-2.5.16.tgz	Direct	2.5.17	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

WS-2018-0162

Vulnerable Library - vue-2.5.16.tgz

Reactive, component-oriented view layer for modern web interfaces.

Library home page: https://registry.npmjs.org/vue/-/vue-2.5.16.tgz

Path to dependency file: /applications/gui/package.json

Path to vulnerable library: /applications/gui/node_modules/vue/package.json

Dependency Hierarchy:

• ❌ vue-2.5.16.tgz (Vulnerable Library)

Found in HEAD commit: 4e5656db54be4b22481fe3774c2caeba51bac190

Found in base branch: main

Vulnerability Details

Vue.js before 2.5.17 vesion in vue poject have potential xss in ssr when using v-bind.

Publish Date: 2018-08-01

URL: WS-2018-0162

Threat Assessment

Exploit Maturity: Not Defined

EPSS:

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

Release Date: 2018-08-01

Fix Resolution: 2.5.17

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.