No, you are not OK. Replace "sh" in that command with "bash" and you should still see the issue. There is a lower likelihood that you'll see the issue, as anyt

No, you are not OK. Replace "sh" in that command with "bash" and you should still see the issue. There is a lower likelihood that you'll see the issue, as anything which just uses sh (including the "system" function, and similar ones) will use dash indeed of Bash; but there will still be places where bash is called explicitly, including many shell scripts that depend on bash features, which are vulnerable.