-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
Ignore extension and parameter names that are property names of `Object.prototype` when parsing the `Sec-WebSocket-Extensions` header.
- Loading branch information
There are no files selected for viewing
9 comments
on commit c4fe466
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be fixed in the 2.x branch of the codebase, there are still many projects out there that rely on 2.x.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got this and 3 other vulnerabilities today
NewOldMax/react-native-validator-form#3
Since running the commands to fix the lower risks, 2 more appeared
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ lodash │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ af08040fa91c155023d3074c1e68edf3f8966db827039473fb05fb92ab8… │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ af08040fa91c155023d3074c1e68edf3f8966db827039473fb05fb92ab8… │
│ │ > plist > xmlbuilder > lodash │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/577 │
└───────────────┴──────────────────────────────────────────────────────────────┘
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ low │ Prototype Pollution │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ deep-extend │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ af08040fa91c155023d3074c1e68edf3f8966db827039473fb05fb92ab8… │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ af08040fa91c155023d3074c1e68edf3f8966db827039473fb05fb92ab8… │
│ │ > metro > jest-haste-map > sane > fsevents > node-pre-gyp > │
│ │ rc > deep-extend │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/612
└───────────────┴──────────────────────────────────────────────────────────────┘
New here, so not sure what to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I keep getting red flag from npm audit
after update, in package.json I have "ws": "^5.1.1", but I get this from the audit:
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High │ Denial of Service │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package │ ws │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in │ >= 1.1.5 <2.0.0 || >=3.3.1 │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ react-native │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ react-native > react-devtools-core > ws │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://nodesecurity.io/advisories/550 │
└───────────────┴──────────────────────────────────────────────────────────────┘
Looks like a typo, Patched in
references "1.1.5" but it should be "5.1.1".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rasmus-storjohann-PG no that is correct. ws@1.1.5
and ws@>=3.3.1
are not vulnerable, all other versions are.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm using version 5.1.1 and still finding it to be vulnerable the same as @rasmus-storjohann-PG .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After upgrading to ws@5.2.0
, I'm still getting the red flag that @rasmus-storjohann-PG reported. Is this a genuine red flag, or is there an issue with how the version number is recognized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All versions above 3.3.0 are not vulnerable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're seeing that red flag because the react-devtools-core
is using a version with this vulnerability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wanted to check, if i use a version above 3.3.0 but react-devtools-core is still using a version with this vulnerability, do i need to worry about the vulnerability? Or is it used in a way that doesn't make it a real issue?
Push