Bash Code Injection Vulnerability
-
Is this also a issue in the Pfsense Firewall's? and when will there be a update or how can we update?
http://www.theregister.co.uk/2014/09/24/bash_shell_vuln/
-
ESF will likely address this soon but bash is not installed in FreeBSD (or pfSense) by default.
I don't know if any packages install it. Apparently not snort, squid, OpenVPN Client Export, iperf, or System Patches.
[2.1.5-RELEASE][root@fw.example.com]/root(1): bash
bash: Command not found. -
It appears that FreeBSD & pFsense isn't vulnerable.
You can check if you're vulnerable by running the following lines in your default shell, which on many systems will be Bash. If you see the words "busted", then you're at risk. If not, then either your Bash is fixed or your shell is using another interpreter.
env X="() { :;} ; echo busted" /bin/sh -c "echo completed"
env X="() { :;} ; echo busted"which bash-c "echo completed" -
Unfortunately the MailScanner package use bash:
/usr/local/bin# ls -la | grep bash
lrwxr-xr-x 1 root wheel 35 Jun 29 09:55 bash -> /usr/pbi/mailscanner-amd64/bin/bash
/usr/local/bin# env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a testI've delete the bash binary, MailScanner is still working but the system is not vulnerably any more.
-
Hmmm
http://stackoverflow.com/questions/26041877/how-to-check-and-upgrade-bash-on-freebsd-related-to-shell-shock-bugHopefully a compiled package will be available soon. A very dirty way to fix it would simply be replacing the binary.
-
There is already a thread for this. See https://forum.pfsense.org/index.php?topic=82163.msg449524#msg449524
