CVE-2017-16028 (Medium) detected in randomatic-1.1.7.tgz - autoclosed

[mend-bolt-for-github[bot]]

CVE-2017-16028 - Medium Severity Vulnerability

Vulnerable Library - randomatic-1.1.7.tgz

Generate randomized strings of a specified length, fast. Only the length is necessary, but you can optionally generate patterns using any combination of numeric, alpha-numeric, alphabetical, special or custom characters.

Library home page: https://registry.npmjs.org/randomatic/-/randomatic-1.1.7.tgz

Path to dependency file: opencov/package.json

Path to vulnerable library: opencov/node_modules/randomatic

Dependency Hierarchy: - webpack-3.10.0.tgz (Root Library) - watchpack-1.4.0.tgz - chokidar-1.7.0.tgz - anymatch-1.3.2.tgz - micromatch-2.3.11.tgz - braces-1.8.5.tgz - expand-range-1.8.2.tgz - fill-range-2.2.3.tgz - :x: **randomatic-1.1.7.tgz** (Vulnerable Library)

Found in HEAD commit: 1e09fcd97fe8494efe02e3cb84540ffba03a2f10

Found in base branch: master

Vulnerability Details

react-native-meteor-oauth is a library for Oauth2 login to a Meteor server in React Native. The oauth Random Token is generated using a non-cryptographically strong RNG (Math.random()).

Publish Date: 2018-06-04

URL: CVE-2017-16028

CVSS 3 Score Details (5.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/157/versions

Release Date: 2018-06-04

Fix Resolution: 3.0.0

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github[bot]]

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

[mend-bolt-for-github[bot]]

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