-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Missing Origin Validation in [email protected] #6109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We should bump #6064 and get it in |
#6064 is in now. I'll see if we can get a patch release out ASAP. |
I am also having this issue and I've looked everywhere. Npm update does not do anything, unless I am entering the command wrong ' npm update webpack-dev-server@latest' ? I'm fairly new to dev so forgive the lack of knowledge. I await the fix. Thank you! Also: I've checked the version of the package and it says its at 3.1.14 which is the latest, however in the package-lock.json is at 3.1.9. |
can you try using @KahtiD
instead, that should install the latest version of the package |
Thanks for the reply! I tried this I just have the vulnerability twice now as its also in package.json. :( Quite a frustrating vulnerability. I've edited my original comment with more information also. |
ah, my bad you can specify the version, in that case you need this
|
Same issue here. Can't fix with "npm audit fix" or upgrading to @latest. |
nor me |
Updating webpack-dev-server doesn't work because there's a typo in the audit repository 🙈 https://npm.community/t/npm-audit-sweems-to-get-semver-wrong/4352/4 |
Same here :( |
|
i published a fork with the patch from #6064. we run audit in CI so was failing our builds. if anybody else wants to use it until the next react-scripts version, it's here: |
I've been away from my project for the day. This is the most frustrating bug lol. Has anyone had a fix yet? I've done all the above and despite the typo being corrected I still get the vulnerability message after |
Is there away to update to 3.1.14 for webpack-dev-server in react-scripts or is it supposed to be at 3.1.9 as it is now, although checking the version returns 3.1.14, confusingly enough. |
Just gave a nudge to @gaearon. Hoping to get a patch out soon. Sorry for the delay! |
Any update on this? |
Waiting... |
Can we have some feedback about the release date of this patch. We deactivated the audit step from our build so as to not block everyone. I know that I can use resolution so as to force the version of the So my main question is about Thanks a lot |
For future reference — my GH notifications are always hosed so please don't count on me seeing a |
I gave @ianschmitz publish rights and he’s working on putting out a release. |
v2.1.3 is available. Please let me know if you have any more issues! |
Running |
@SafiaNuzhath it looks like you are using Angular, this is the React repository. I would recommend you to leave a comment in the Angular thread related to the security issue. |
I am still having the same problem. I get the error C:\Users\virus\node_modules\webpack-dev-server (version: 3.1.9) I tried npm audit fix. Deleting modules then updated json file to "webpack-dev-server": "3.1.14" then npm install. Still not working any ideas? npm 6.5.0 |
the problem is solved thanks a lot |
issue solved thank you guys |
Is this a bug report?
Yes, NPM reports 1 high severity vulnerability when running
npx create-react-app my-app
. Not sure why I can't find a bug report already about this issue. Sorry if it has already been reported.According to
npm audit
, thewebpack-dev-server
dependency has to be upgraded to>=3.1.11
.Environment
Steps to Reproduce
The text was updated successfully, but these errors were encountered: