uniquelyparticular / serverless-oauth

A Particularly minimal pluggable OAuth implementation using Serverless.
https://uniquelyparticular.com
MIT License
1 stars 2 forks source link

WS-2019-0331 (Medium) detected in handlebars-4.1.2.tgz - autoclosed #123

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

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

WS-2019-0331 - Medium Severity Vulnerability

Vulnerable Library - handlebars-4.1.2.tgz

Handlebars provides the power necessary to let you build semantic templates effectively with no frustration

Library home page: https://registry.npmjs.org/handlebars/-/handlebars-4.1.2.tgz

Path to dependency file: serverless-oauth/package.json

Path to vulnerable library: serverless-oauth/node_modules/handlebars

Dependency Hierarchy: - semantic-release-15.13.14.tgz (Root Library) - release-notes-generator-7.1.4.tgz - conventional-changelog-writer-4.0.3.tgz - :x: **handlebars-4.1.2.tgz** (Vulnerable Library)

Found in HEAD commit: e45ef645b834c42d08442b44219ebe3f718e535e

Vulnerability Details

Arbitrary Code Execution vulnerability found in handlebars before 4.5.2. Lookup helper fails to validate templates. Attack may submit templates that execute arbitrary JavaScript in the system.

Publish Date: 2019-11-13

URL: WS-2019-0331

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/1316

Release Date: 2019-12-05

Fix Resolution: handlebars - 4.5.2


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: #124

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: #124

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: #124