Vulnerable Regular Expression

[cristianstaicu]

The following regular expression used in parsing the JSON file is vulnerable to ReDoS:

/\s+$/

The slowdown is moderately low: for 50.000 characters around 2 seconds matching time. However, I would still suggest one of the following:

• remove the regex,
• anchor the regex,
• limit the number of characters that can be matched by the repetition,
• limit the input size.

If needed, I can provide an actual example showing the slowdown.

[AliSawari]

@cristianstaicu Yeah I noticed that too , as Snyk warns me about them vulnerabilities 😄
I don't have a serious app using this lib but I'm concerned about further uses 🤔

@get will be there any patches ?!

[AliSawari]

parsejson is a Method that parses a JSON string and returns a JSON object.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. An attacker may pass a specially crafted JSON data, causing the server to hang.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a Regex string and cause the service to hang for a large periods of time.

text quoted from snyk vuln page : Link

[joshwiens]

It's also worth noting that anyone that uses snyk / nsp & socket.io-client has broken client builds

[AliSawari]

@d3viant0ne WOW , didn't expect that coming, Why's that?

[joshwiens]

If you run the nsp or snyk checks in a CI run as a part of your validations, you get a non zero exit code, thus broken as parsejson is a nested dependency of socket.io-client

[rgeraldporter]

Any plans to fix this?

[alexw10]

Anyone have an update on this anyone? Need a fix soon since some packages we use are using this and is out of our control. Our company's security group is needing this fixed.

I am willing to help out as well and or try to fix this.

[CSobol]

Is there a reason you can't just replace line 20 with data = data.trim()?

I want to issue an MR, but if you have compatability concerns then it's not as simple I suppose.

[vaikzs]

Is there a fix for this?

[soundasleep]

If you're coming in here from an audit log/warning: this package looks to be essentially unmaintained, and in any case your packages, and their dependencies, should be using JSON.parse(...) rather than this package.

You might need to hunt through your package-lock.json dependencies to find which dependency is relying on parsejson: in my case, I needed to upgrade browser-sync.

[HansUXdev]

@cristianstaicu you seem the most familiar with this. Would you (or anyone else) be willing to submit a PR with a patch and or fork the repo with a patch if this repo isn't maintained?

[kmturley]

In my case I did:
npm ls parsejson

Which outputted:

[email protected]
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └─┬ [email protected]
        └── [email protected]

And fixed using:
npm install [email protected]

[Flink91]

I had this problem - for future visitors:
If you are using the "socketio" package, change to "socket.io", those are different.

[tibbon]

This is a CVE with a HIGH rating, and is still open?

[pertrai1]

I am getting a HIGH rating on a project I started working on:

https://nvd.nist.gov/vuln/detail/CVE-2017-16113

[pcolusso]

Hey everyone, as mentioned above this package looks like it's clearly unmaintained. I recieved this secuirty warning as a knock-on affect of another unmaintained package. Was able to track down the root cause via yarn why recommend to anyone else viewing this to do the same, and cut out whatever package is requesting this. Yarn's Selective Dependency Resolutions is also quite helpful if you need to force override a package's version that may be still using this module.