Security Update 2003-08-14 Released 63
Delta-9 writes "Today, Apple released Security Update 2003-08-14, which '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.'" It's on Software Update, and will likely soon appear on the support downloads page.
Good work Apple (Score:5, Interesting)
Some info about the vulnerability (Score:3, Informative)
Re:Some info about the vulnerability (Score:1, Flamebait)
Re:Some info about the vulnerability (Score:5, Informative)
But that's okay. Don't let the facts get in the way of your skreed. Carry on.
Re:Some info about the vulnerability (Score:2)
Re:Some info about the vulnerability (Score:3, Informative)
However, if you use os x just stick with the stock ftpd since it's not wu-ftp. Like I said earlier, the bug wasn't with the ftpd, it was a library call. Just run software update and get on with your life.
Re:Some info about the vulnerability (Score:2)
Since I don't run an FTP server, I couldn't tell you for sure. I believe that ProFTP is supposed to be fairly capable. I also note that OpenBSD seems to lean toward PureFTP [pureftpd.org]. Not sure what to make of that, but given the OpenBSD philosophy towards security, I'd say it's probably not a bad choice.
Re:Some info about the vulnerability (Score:1)
Re:Some info about the vulnerability (Score:1)
Re:Some info about the vulnerability (Score:5, Informative)
The realpath() function from bsd calculates the length of a resolved directory path. The problem is an off by one error. It actually affects more than than just an ftp deamon since it's a library function, just like the gzip vulnerabilty a while ago. See the sans report [neohapsis.com] for more info.
3 days from disclosure to security update is pretty good though.
Re:Some info about the vulnerability (Score:2)
The SANS report is just a summary of current vulnerabilities. While that issue of the report was published on August 11, the vulnerability itself was first published on July 31 [cert.org]. Apple was a bit slow on this one for some reason...
Ok, people. I'm really sorry. (Score:5, Informative)
It looks like I jumped the gun on this...On several levels...
First, wu-ftpd is not the ftp server in Mac OS X. lukemftpd is.
Second, the most relevant advisory is not the quoted one, but this one (which previously appeared on Slashdot): FreeBSD-SA-03:08.realpath [freebsd.org].
As the name implies, the bug originates from FreeBSD, and potentially leaves a long list of programs vulnerable (listed in the advisory).
This means that the problem is broader than my original message anticipated. It means that other remote services may be vulnerable, including sftp.
Thanks to the anonymous user who brought my attention to my (pretty bad) mistake.
Please spread this information instead of the wrongful information in the parent post. Mod parent down.
Re:Some info about the vulnerability (Score:5, Insightful)
The East Coast has reverted to the stone age, my Windows machine is insulting me, but there's Apple with another Security Update for a *potential* weakness...
Damn, you've got to admire their timing
Re:Dear Apple (Score:1, Funny)
Signing???? (Score:1)
Beware of updating... (Score:1, Offtopic)
Re: (Score:1)
Re:Beware of updating... (Score:1, Informative)
Not here: (Score:3, Interesting)
But, I only use Navigator on rare occasions; testing session based problems was the order of the day today.
Re:Beware of updating... (Score:1)
Re:Beware of updating... (Score:1)
Re:Beware of updating... (Score:1)
Re:Beware of updating... (Score:2)
Re:Beware of updating... (Score:1)
Odd Side Effect?! (Score:3, Interesting)
Zoom Zoom! (Score:1, Offtopic)
It's amazing how fast that download went, what with half the computers in the U.S. offline. Slashdot, on the other hand, is crawling for some reason. Could be that most of Ontario still doesn't have power, so there are fewer local links to the backbone.
OSX 10.1.5? (Score:3, Interesting)
My reading of the issue on the FreeBSD advisory [freebsd.org] is that it is likely 10.1.x is affected by this too.
Can anyone confirm?
Is a fix from Apple likely? I would find it very disappointing if Apple have stopped issuing security fixes for this OS - even Microsoft support their previous generation products (Windows 2000 Professional, for example).
If not, given this affects the (open-source) Darwin core of the OS, is a patch to the affected library/ies a possibility?
Re:OSX 10.1.5? (Score:1)
The advisory states that ftpd is not affected by the bug.
So at least that deamon isn't vunerable. But others can be. It would be nice to have apple release an update for these systems.
Not Panther (Score:3, Informative)
Furthermore, I just noticed that the installer said; "The installer needs to run a program to determine if it can be installed. Do you want to continue?" - that's a cool security feature!
Oh, and the update is now up on Apple's downloads page [apple.com]
Reboot Reqired (sigh) (Score:4, Interesting)
And they do require them,as I discovered last night. I wanted to install 10.2.0 on another machine. Rather than try to download a whopping 100Megs of updates, I would use the 6 mini updates I already had to upgrade the computer to 10.2.6. And rather than repeat the install-reboot cycle a half dozen times, I would mount the other machine as a Firewire drive on my 10.2.6 machine. No reboots required, right?
Well, half an hour later, with the 10.2.6 upgrades installed, I boot up. Nothing except a grey screen with an Apple logo. No cyclic symbol. The only way to solve the problem was to reinstall 10.2.0, and upgrade piecemeal, rebooting each time.
Re:Reboot Reqired (sigh) (Score:5, Interesting)
In the case of a security update that changes libraries, though, it's prudent to reboot, or at least shut down any daemon processes and restart them.... Anything newly launched will be bound to the new library, but anything already running will continue using the old one, hence any program that uses the buggy function needs to be restarted. A reboot is certainly the easiest way. :-)
Re:Reboot Reqired (sigh) (Score:2, Insightful)
More often than not, the reboots are *technically* unnecessary. Sometimes the reboots are just to ensure some daemon gets reloaded correctly and by the correct parent process. It could be done with a script, but could easily be foiled by the unknown state of any given user's machine.
Finally, sometimes reboots are necessary because they are replacing/updating the kernel itself. IANAKE (I am not a kernel engineer), but I have heard that not all kernel alterations can be done without reboot.
For the record,
Re:Reboot Reqired (sigh) (Score:3, Insightful)
Yeah, you know what else sucks? I have to turn off my car to work on the engine. Its a huge pain in the ass, you gotta get out and walk around....
In seriousness, OS X is sooo much better than OS 9 in this regard. Device drivers don't usually need a reboot, just security updates and really low-level stuff... and these are things you want to reboot for, to take advantage of the improvements!
Besides, if you want to, you
SMB problems?!? (Score:1)
Well, I ran this security update this morning, and the XP security updates a few days ago, and now my PowerBook and Compaq refuse to talk to each other. It seems one update or the other broke SMB between the 2 platforms, because it worked fine last week.
Now, after I try to connect to the XP box, it tries & then won't do it. A few moments later, it gives me that very annoying, very modal dialog box that grays out everything else, and says (in several languages) that I need to reboot. Ugh! Anyone
Re:SMB problems?!? (Score:2)