Actually, about 21 of them were Apple issues, although admittedly
there was a fair bit of overlap/similarity among many of them
(permissions related attack vectors, format string vulnerabilities
At the risk of writing a novel here, my own personal hope is that
Apple and its user community can foster better relations with the
people finding and fixing security problems in the future. Step one,
communicate _collaboratively_ since everybody wants better security at
the end of the day. (Corollary to step one, don't claim that
everything is a non-issue for some contrived reason and that everyone
but you is obviously an idiot.) Talented folks volunteering to lend OS
X programming/reversing skills where available to a project like ZERT
could also be a real win if they're interested.
Back to your post... the beachball was due to an embedded JPEG2000
graphic that CoreGraphics can't deal with. (see previous thread at
Note that the currently released Safari is not a vector for attack.
Ack, at 2/2/07, jpel...@gmail.com said:
>Did the Apple QT security update fix only #1 or #1 + #3?
Technical Support/Carbon troll/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
right, in fact only 7 are not related to Apple.
but most of these bugs are just that, bugs, not security issues, they
require access to the local machine, and rarely cause anything more
than a crash.
i did not read the details about all of them, but i checked a few,
MOAB 1 is supposed to allow you to execute code at a specific
location, i could not reproduce that, it executed code (bad enough),
but the program counter was not pointing to "deadbabe" as was
there are thousands of similar bugs, most applications don't run well
when u open corrupted documents.
The continued characterization of potential problems with OS X and its
applications as "not real security issues, just a bug" does a
disservice to the people working to find them by insulting their work,
a disservice to the user community by keeping them ignorant, and a
disservice to developers by encouraging laziness. To quote Jon
Stewart, "Please stop, you're hurting America."
> i did not read the details about all of them, but i checked a few,
> MOAB 1 is supposed to allow you to execute code at a specific
> location, i could not reproduce that, it executed code (bad enough),
> but the program counter was not pointing to "deadbabe" as was
There is a variety of interesting work that has been done about
targeting exploit code like this.
Linux, OpenBSD and Windows Vista share an interesting related feature
called "address space layout randomization," such that it loads the
pieces of programs into memory in a random fashion in order to make
guessing attack vectors much harder. There is a blog post about it
There is also a good wikipedia entry about it here:
It would be nice to see Apple include this in a 10.5.x or 10.6 release
since it makes it somewhat harder to do something useful with injected
> there are thousands of similar bugs, most applications don't run well
> when u open corrupted documents.
Then those applications are broken. Malformed user input should not be
able to cause a crash. Those who have written or work regularly with
network services have learned this lesson many, many times over.