Security Update 2003-08-14 addresses a potential vulnerability in the fb_realpath() function which could allow a local or remote user to gain unauthorized root privileges to a system.
The 1.1MB update is available via the Software Update function in Mac OS X or via the Web.
Security Update 2003-08-14 v.1.0 Server is also available.
More info here.
The iPhone 18 Pro’s expected color options for 2026 include a striking new signature shade called “Dark Cherry” — a deep, wine-like red…
India’s government has dropped a proposal that would have required Apple, Samsung, and other smartphone makers to pre-install the country…
“Margo’s Got Money Troubles” — a new Apple TV series, based on the novel by Rufi Thorpe, was made by people who know good TV…
In a notable shift, BNP Paribas analyst David O’Connor upgraded Apple (AAPL) to Outperform (“Buy”) from Neutral and raised the price target…
Starting with iOS 26.4, Apple now supports AI chatbot apps on the iPhone via CarPlay.ChatGPT was the first to add support shortly…
I remember reading here once where some obvoius PC troll had the nerve to criticize Apple for posting so many security updates for OSX. In light of the latest worm attack in Microsoft-land, I’m wondering how much barbecue sauce that person has put on the crow he’s now eating…
” width=”19″ height=”19″ alt=”wink” style=”border:0;” />)
Well, so far this year there have been 6 security updates for OS X. Meanwhile there have been 31 Windows patches in 2003 alone, and there were 72 of them in 2002.
Do Apple have a team of people deliberately trying to break OSX, so they can fix the patch, or is this a generic UNIX error that someones told them about?
Heh…I like the CROW comment. ;o)
I did notice a significant drop in the number of Wintel TROLLS on this site when the worm started propagating.
All I can say is that it couldn’t have happened to a more deserving bunch. ;o)
I think the difference is, the OSX updates are more pre-emptive in nature, whereas the Microsoft patches are for already infected machines, correct?
Do Apple have a team of people deliberately trying to break OSX, so they can fix the patch, or is this a generic UNIX error that someones told them about?
Apple is based on an open source layer, where many components is shared with Linux, Freebsd, Open and/or Netbsd. Some groups go over open source code to proactively search for potential security bugs. Openbsd is a good example of this, where they try to check every single line of code. There are also companies that pay people to go over code to search for security problems, and you have offcourse the people that happen to stumble on problems.
Any security expert will tell you that you are better off with open source code.