First published: Thu Apr 26 2018(Updated: )
Affected versions of `sync-exec` use files located in `/tmp/` to buffer command results before returning values. As `/tmp/` is almost always set with world readable permissions, this may allow low privilege users on the system to read the results of commands run via `sync-exec` under a higher privilege user. ## Recommendation There is currently no direct patch for `sync-exec`, as the `child_process.execSync` function provided in Node.js v0.12.0 and later provides the same functionality natively. The best mitigation currently is to update to Node.js v0.12.0 or later, and migrate all uses of `sync-exec` to `child_process.execSync()`.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/sync-exec | <=0.6.2 | |
sync-exec | <=0.6.2 | |
Langgenius Dify Node.js | <0.11.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-16024 has a moderate severity level due to its potential to expose sensitive command results to low privileged users.
To fix CVE-2017-16024, update the sync-exec package to version 0.6.3 or later where the vulnerability is addressed.
CVE-2017-16024 affects users of the sync-exec package versions up to and including 0.6.2.
The impact of CVE-2017-16024 includes the risk of unauthorized access to command output by low privilege users due to improper file permissions.
CVE-2017-16024 impacts the sync-exec npm package and any Node.js applications using it, particularly those relying on versions up to 0.6.2.