chore(versioner): attempt to prevent blatantly unsafe external versioner commands (fixes #10721) (#10722)
While preparing the command, attempt to verify that the template expansion happens in a way that will result in a non-shell-injection command. I don't presume to say that this is a 100% prevention, and the script itself can always do dumb shit with the file path later. Nonetheless, we should make a best-effort attempt. Equally, this could generate false positives for commands that are strangely written but in fact safe. I think this is acceptable; external versioning is currently used by approximately 0.02% of users, and presumably most of them have a setup that is sane. --------- Signed-off-by: Jakob Borg <jakob@kastelo.net>
This commit is contained in:
@@ -76,6 +76,39 @@ func TestExternal(t *testing.T) {
|
||||
}
|
||||
}
|
||||
|
||||
func TestExternalCommandSplit(t *testing.T) {
|
||||
e := external{
|
||||
filesystem: fs.NewFilesystem(fs.FilesystemTypeFake, "TestExternalCommandSplit"),
|
||||
}
|
||||
|
||||
cases := []struct {
|
||||
cmd string
|
||||
safe bool
|
||||
}{
|
||||
{`echo %FOLDER_PATH% %FILE_PATH%`, true},
|
||||
{`echo "%FOLDER_PATH% %FILE_PATH%"`, false},
|
||||
{`echo %FOLDER_PATH%/%FILE_PATH%`, true},
|
||||
{`echo "%FOLDER_PATH%/%FILE_PATH%"`, true},
|
||||
{`echo '%FOLDER_PATH%/%FILE_PATH%'`, true},
|
||||
{`echo "'%FOLDER_PATH%/%FILE_PATH%'"`, false},
|
||||
{`sh -c "echo '%FOLDER_PATH%/%FILE_PATH%'"`, false},
|
||||
{`sh -c "echo %FOLDER_PATH%/%FILE_PATH%"`, false},
|
||||
}
|
||||
|
||||
for _, tc := range cases {
|
||||
e.command = tc.cmd
|
||||
res, err := e.prepareCommand("evil file name")
|
||||
if tc.safe && err != nil {
|
||||
t.Fatal(err)
|
||||
}
|
||||
if !tc.safe && err == nil {
|
||||
t.Logf("%q", res.Path)
|
||||
t.Logf("%q", res.Args)
|
||||
t.Errorf("should be unsafe: %q", tc.cmd)
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
func prepForRemoval(t *testing.T, file string) {
|
||||
if err := os.RemoveAll("testdata"); err != nil {
|
||||
t.Fatal(err)
|
||||
|
||||
Reference in New Issue
Block a user