Step 1 - fix the ownership

$ sudo chown -R root:admin /Applications/Microsoft\ Office\ 2008/

Step 2: fix the executables file permission

$ sudo find /Applications/Microsoft\ Office\ 2008/ -type f -exec chmod 664 {} \;

$ sudo find /Applications/Microsoft\ Office\ 2008/ -type f | while read foo; do file “${foo}” | while read bar; do echo “${bar}” | awk -F: ‘/Mach-O/ {printf “chmod 775 “%s”\n”,$1}’; done; done | grep -v “for architecture” | sudo sh

Hope I didn’t miss something..

/usr/bin/sudo /bin/chmod -R a-st /Applications/Microsoft\ Office\ 2008 /Library/Automator /Library/Fonts/Microsoft /Library/Application\ Support/Microsoft

/usr/bin/sudo /usr/sbin/chown -h -R root:admin /Applications/Microsoft\ Office\ 2008 /Library/Automator /Library/Fonts/Microsoft /Library/Application\ Support/Microsoft

Full post at:
http://www.officeformac.com/blog/Security-issue-in-Mac-Office-2008-Installer

So now for your fixes, Jim, I reworked them a bit, didn’t need sudo’s to find the files, just to chmod them, also I went with xargs for speed, right Rick? (and does speed up the first)

Step 1: Knock all files down to rw-rw-r–
find /Applications/Microsoft\ Office\ 2008 -type f -print0 | xargs -n 1045 -0 /usr/bin/sudo chmod 664
find /Library/Application\ Support/Microsoft -type f -print0 | xargs -n 890 -0 /usr/bin/sudo chmod 664
# or just simply take away x for the fonts
sudo chmod a-x /Library/Fonts/Microsoft/*
#automator contains not Mach-O executables, only Applescripts that only require read access
find /Library/Automator -type f -print0 | xargs -n 1045 -0 /usr/bin/sudo chmod a-x

Note: -n 1045 is to prevent an error when sudo when it gets too many arguments, apparently xargs heaps them on a bit too much, longer paths means less arguments are able to be fit in

Step 2: Now find all files of Mach-O type and bump them back up to rwx-rwx-r-x
find /Applications/Microsoft\ Office\ 2008 -type f | while read foo; do file "${foo}" | while read bar; do echo "${bar}" | awk -F: '/Mach-O/ {print $1}' | grep -v "for arch"; done; done | xargs -I '{}' /usr/bin/sudo chmod a+x '{}'
find /Library/Application\ Support/Microsoft -type f | while read foo; do file "${foo}" | while read bar; do echo "${bar}" | awk -F: '/Mach-O/ {print $1}' | grep -v "for arch"; done; done | xargs -I '{}' /usr/bin/sudo chmod a+x '{}'

The second still takes a while with all the awk and file calls on each file… but what else are you gonna do? The awk filtering works well, though, I like that. Anyhoo, it does get the job done, thanks for the push Jim!

Although now that I think of it, why would one really want write access to an executable anyway? Apart from some self modifying code for copy protection ofrserialization, it’d seem that r-x is all you really need to run a program eh? So for the more paranoid:

Find all files of Mach-O type and chmod them to r-x-r-x-r-x
find /Applications/Microsoft\ Office\ 2008 -type f | while read foo; do file "${foo}" | while read bar; do echo "${bar}" | awk -F: '/Mach-O/ {print $1}'
| grep -v "for arch"; done; done | xargs -I '{}' /usr/bin/sudo chmod 555 '{}'

PS. ‘Find all files of Mach-O type and chmod them to r-x-r-x-r-x’ - uh don’t you want ‘r-x-r-x—x’?

Bleach supposedly leaves a bad aftertaste; maybe Ethan could enlighten us on that part.