

Impact: A sandboxed application may be able to circumvent sandbox restrictionsĭescription: An unvalidated array index issue existed in the Dock’s handling of messages from applications.

Impact: A remote attacker may be able to gain access to another user's sessionĭescription: cURL re-used NTLM connections when more than one authentication method was enabled, which allowed an attacker to gain access to another user's session. This issue was addressed through improved bounds checking.ĬVE-2014-1370 : Chaitanya (SegFault) working with iDefense VCPĪvailable for: OS X Mavericks 10.9 to 10.9.3 Impact: Opening a maliciously crafted zip file may lead to an unexpected application termination or arbitrary code executionĭescription: An out of bounds byte swapping issue existed in the handling of AppleDouble files in zip archives. The complete list of certificates may be viewed at. Impact: Update to the certificate trust policyĭescription: The certificate trust policy was updated.

Summary: it's not an entirely a meaningful question, but to the extent that it's meaningful Mavericks is a 64-bit OS.Available for: OS X Lion v10.7.5, OS X Lion Server v10.7.5, OS X Mountain Lion v10.8.5, OS X Mavericks 10.9 to 10.9.3 10.6, for example, would install exactly the same on a 32- or 64-bit computer, and then decide at runtime which mode each program should run in. Note that there've never been separate 32- and 64-but versions of OS X. The most visible example of this is the System Preferences, which normally runs in 64-bit mode, but can quit & relaunch itself in 32-bit mode to run old 32-bit-only preference panes (if you can still find one). But it's still fully capable of running old 32-bit programs, and there are even a number of system programs that can run in either mode (again, to provide compatibility with old 32-bit software). Starting in 10.8, Apple removed the 32-bit versions of the kernel and most built-in apps, meaning that it'll only run on 64-bit CPUs. Over the history of OS X, it's gradually morphed from 32-bit only (through 10.2 I think), to fully 32+64-bit capable (10.6), to mostly-64-bit-only (10.8-10.9). It also has a multi-architecture binary format, so a single program can include both 32- and 64-bit code, and the OS will simply run it in whatever seems to be the most appropriate mode at the moment. OS X doesn't really have a single overall mode - it can easily run different components (different processes, the kernel, etc) in different modes.
