Injecting a dynamic shell in chroot is dangerous

I need to put /bin/sh in the chroot so I can run the command with its environment and cwd. To do that, I just copy /bin/sh **plus its dynamic dependencies (determined by ldd)**.

However these libs might be different from the ones that have certainly been packed. If they are, bad things will happen.

A solution would be to inject a statically-linked shell (like busybox) or to not use a shell (how!?).