question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Vulnerability: Denial of Service ('ws' and 'mem') and Memory Leak ('inquirer')

See original GitHub issue

We use Sourceclear (sourceclear.com) to scan our app code and the following vulnerabilities were reported:

  1. Denial of Service (DoS) for ws(v1.1.5)

    Transitive Dependency:

    This issue was fixed in version 3.3.1 of ws. That version is currently considered safe, we suggest that you upgrade to the fixed version.

    Dependency Graph: react-native 0.60.3 > @react-native-community/cli 2.9.0 > ws 1.1.5

  2. Denial of Service (DoS) for mem(v1.1.0)

    Transitive Dependency:

    This issue was fixed in version 4.0.0 of mem. That version is currently considered safe, we suggest that you upgrade to the fixed version.

    Dependency Graph: react-native 0.60.3 > @react-native-community/cli 2.9.0 > metro 0.54.1 > metro-inspector-proxy 0.54.1 > yargs 9.0.1 > os-locale 2.1.0 > mem 1.1.0

  3. Memory Leak for inquirer(v3.3.0)

    Transitive Dependency:

    We do not have a confirmed fix for this issue yet. However, newer versions of the library have been released. We suggest that you upgrade to 6.5.0, which is considered safe.

    Dependency Graph: react-native 0.60.3 > @react-native-community/cli 2.9.0 > inquirer 3.3.0

React Native version: 0.60.3

Note: library versions of ws, mem and inquirer that come with the latest RN release (v0.61.5) are also not at the recommended versions

Steps To Reproduce

  1. Need to install and activate licensed account of SourceClear
  2. scan repo code using cli or other supported mediums (for example: srcclr scan --url https://github.com/srcclr/example-ruby)

Hoping this is the ideal place to be reporting these (Please redirect if I’m wrong) And if I am at the right place, please do acknowledge and confirm timelines if this seems actionable

Thank You

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:3
  • Comments:7

github_iconTop GitHub Comments

2reactions
Ananthakrcommented, Nov 17, 2020

@gabrielmoncea ws issue is still showing on RN 0.63.2

0reactions
gabimonchacommented, Sep 7, 2020

@ivgraai does it show on RN 0.63.2 ?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Memory leak - OWASP Foundation
A memory leak is an unintentional form of memory consumption whereby the developer fails to free an allocated block of memory when no...
Read more >
CVE-2019-19078 Detail - NVD
This vulnerability has been modified and is currently undergoing reanalysis. Please check back soon to view the updated vulnerability summary.
Read more >
Software Security | Memory Leak - Fortify Taxonomy
Most memory leaks result in general software reliability problems, but if an attacker can intentionally trigger a memory leak, the attacker might be...
Read more >
CWE-401: Missing Release of Memory after Effective Lifetime
Memory leaks have two common and sometimes overlapping causes: Error conditions and other exceptional circumstances; Confusion over which part of the program is ......
Read more >
https://huggingface.co/yuningm/bart-large-citesum/...
In REF, a formal method for modeling semantic denial of service attacks against ... is presented to support scratchpad memories at a high...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found