-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Command Injection #4490
Comments
@dev2games Thanks for posting, we'll take a look as soon as possible. For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her minions in Austin, click here. |
This is a security vulnerability in sails-generate, meaning that you'd be able to hijack your own computer when running |
Hello, This vulnerability led me here too, and it would seem like it it not only in sails-generate, but also in sails itself:
The problem is fixed in the newest versjon of machine-pack (v4.x) where it has migrated to using opn as the replacement for open, which is deprecated. |
I'm also getting this issue after install It seems to be documented in issue #4402 as well. Sails version: 1.1.0
So am I seeing that this is not actually a critical issue and can be safely ignored for now? |
@oaksofmamre @raqem I've added a PR in 'sails-generate' to bump the 'machinepack-process' version to the latest, as both my manual test, and the automatic tests show no breaking changes between v2.0.2 and v4.0.0 for sails. Aparently it is only used when generating a new sails app ('sails new') to run the 'npm install' command after the files and directories are generated. This should fix both critical vulns reported by 'npm audit' |
Is there a timeline when this can be fixed? I see there is already a PR by @hakash to fix the vulnerabilities |
@dev2games @oaksofmamre @hakash @matdombrock @PavanBahuguni - Sails is currently working on the patch for this 👍 |
@dev2games @hakash @matdombrock @PavanBahuguni In addition, please see #4699 (comment) and #4402 (comment). |
Oh hey again, @dev2games. Now that this issue is reopened, we'll take a fresh look as soon as we can! Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly. For help with questions about Sails, click here. |
@wulfsolter it's because I accidentally reopened it while logged in as sailsbot (I realized after closing it it'd be better to wait until we're through with our current purge before closing these vulnerability-related issues) Also re the new message: sailsbot's new MO is that instead of parroting the same thing she says on initial opening, she responds to any reopening of issues and PRs with a shorter, sweeter message (mainly just to remind folks of the two points in the little footer thingie) |
@dev2games @hakash @matdombrock @PavanBahuguni Multiple related PRs for this were merged a day ago - how is the behaviour now? I welcome the rest of the community to test this out as well 👍 |
Removed
The text was updated successfully, but these errors were encountered: