eldorplus / laravel-elixir-clean-unofficial

Laravel Elixir Cleanning Extension
1 stars 0 forks source link

WS-2019-0025 (Medium) detected in marked-0.3.19.js - autoclosed #158

Closed mend-bolt-for-github[bot] closed 3 years ago

mend-bolt-for-github[bot] commented 3 years ago

WS-2019-0025 - Medium Severity Vulnerability

Vulnerable Library - marked-0.3.19.js

A markdown parser built for speed

Library home page: https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.19/marked.js

Path to dependency file: laravel-elixir-clean-unofficial/node_modules/marked/www/demo.html

Path to vulnerable library: laravel-elixir-clean-unofficial/node_modules/marked/www/../lib/marked.js

Dependency Hierarchy: - :x: **marked-0.3.19.js** (Vulnerable Library)

Found in HEAD commit: ad004d8380ed05404f972ceefd6529e3a89c49b1

Found in base branch: master

Vulnerability Details

Versions 0.3.7 and earlier of marked When mangling is disabled via option mangle don't escape target href. This allow attacker to inject arbitrary html-event into resulting a tag.

Publish Date: 2017-12-23

URL: WS-2019-0025

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://github.com/markedjs/marked/commit/cb72584c5d9d32ebfdbb99e35fb9b81af2b79686

Release Date: 2019-03-17

Fix Resolution: 0.3.9


Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 3 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #161

mend-bolt-for-github[bot] commented 3 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #161

mend-bolt-for-github[bot] commented 3 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #161

mend-bolt-for-github[bot] commented 3 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #161