Essentially, like in http://osxdaily.com/2012/04/05/how-t...-in-mac-os-x/:
I still smell BS statistics and scare tactics deployed by anti-virus companies for the numbers telling that "several hundred thousand older Macs have been affected".Launch Terminal (found in /Applications/Utilities/) and enter the following commands:
defaults read /Applications/Safari.app/Contents/Info LSEnvironment
If you see a message like “The domain/default pair of (/Applications/Safari.app/Contents/Info, LSEnvironment) does not exist” proceed to the next defaults write command:
defaults read ~/.MacOSX/environment DYLD_INSERT_LIBRARIES
If you see a message similar to “The domain/default pair of (/Users/joe/.MacOSX/environment, DYLD_INSERT_LIBRARIES) does not exist” then the Mac is NOT infected.
Sort of the same type of numbers and mutant statistics that a while back mentioned how an average woman eats 4-7 lb of lipstick in her lifetime. When you break back the numbers of how much an average woman "eats" lipstick a year, it would come to at least 1.5 oz which would be, if the lipstick are the same size as average lip balms, count to 10 lipsticks. A year. So a lipstick a month, eaten and not used as a lipstick?
Just based on how much lipstick is reported sold does not count that the women eat it all.
Just because there are several hundred thousand older Macs around it does not mean they were all affected, or even that would all have had laid-back java settings in them.
Anyway. Back to vulnerabilities and potential vulnerabilities... they still pretty much remain the same on Macs:
1. Java (aka Java platform - not a Mac OS X specific issue)
3. Flash (aka a Flash issue - definitely not a Mac OS X specific issue)
4. Microsoft Office macros (aka a MS issue - not a Mac OS X specific issue)
5. Trojans and other bad stuff downloaded/installed by user - these have been often from some weird P2P program (user issue)
6. User issues (command line acrobatics, allowing a child to use an administrator account, user removing some stuff they shouldn't, using a rotten AppleScript or Automator script, or installing something themselves - user issues)
7. User settings, or sometimes default settings (e.g. automatic login, using an administrator account for everything, having bad passwords) <-- these are potential hazards if the Mac gets to wrong hands
8. Mac OS X settings (e.g. in 10.7 no admin password is no longer required for system updates... that Software Update downloads from Apple's site) <-- some of these could have some potential