A month-long campaign by two independent security researchers to disclose security flaws in Apple’s products has so far resulted in 10 vulnerabilities being publicly disclosed – and several more on the verge of being announced. Exploit information has also been published along with proof-of-code detailing how to take advantage of the flaws, several of which were described as being remotely exploitable by the researchers.
The disclosures are part of a Month of Apple Bugs (MoAB) effort launched on 1 January 2007by independent security researcher Kevin Finisterre and another researcher identified only by the initials LMH.
The goal of the effort, identical in nature to the Month of Kernel Bugs and Month of Browser Bug campaigns in 2006, is to raise public awareness of security issues in Apple’s products, according to Finisterre. “[Apple’s] creating commercials claiming to be secure and the user base feels like they are wearing a suit of armour,” Finisterre said via email. In reality, “there’s NO lack of bugs on OSX from both an application and platform standpoint.”
Finisterre said that while only 10 flaws have been publicly disclosed so far, he “has lost count” of the number of vulnerabilities that have been discovered as part of the MoAB effort. “Finding an abundance of bugs has been no problem at all [but] not all of them are easily exploitable.”
According to Finisterre, several of the vulnerabilities stem from Apple's inadequate documentation for various Application Programming Interfaces (APIs) related to functions commonly used for displaying error messages. “Several developers are misusing the functions and that is leading to potentially exploitable situations,” Finisterre said.
Dave Marcus, security researcher and communications manager for McAfee Avert Labs, said that the effort to find Apple bugs appears to be succeeding in raising awareness of security issues on the platform.
But so far, at least, none of the disclosed vulnerabilities appear to be “showstoppers,” Marcus said. In fact, the only flaws that appear to be “interesting” is one affecting QuickTime that allows for arbitrary code execution and an Adobe PDF flaw that affects multiple operating environments, including the Mac OSX, he said. “They are interesting because they affect products that are commonly and widely used,” Marcus said.
The decision by Finisterre and LMH to publicly disclose flaws before giving Apple a chance to address them has raised the risk for users, Marcus said. But the efforts by an ex-Apple engineer named Landon Fuller to issue fixes for each of the flaws being disclosed is mitigating some of that risk, he said.
Fuller did not immediately respond to a request for comment. But his fixes and workarounds for the flaws are posted at landonf.bikemonkey.org/.
Apple itself has not released any patches for the flaws and did not discuss how it would respond to the disclosures. In a brief e-mailed statement, a spokesman for the company said that Apple "has a great track record of addressing potential security vulnerabilities before they can affect users," but did not offer any elaboration.
The statement also noted that Apple welcomes feedback on improving security for the Mac platform.
Efforts such as the Month of Apple Bugs initiative can be useful in raising awareness of security problems with platforms such as Mac OS X, said Charles King, an analyst with the Pund-IT consultancy.
“Apple has historically had fewer problems with security breaches than the Wintel platform,” with some security experts saying that's at least partially true because it has a much smaller user base, King said. A concerted effort to find flaws in its software could push Apple to pay more attention to security – much as Microsoft Corp. has been forced to do, he said.
At the same time, care needs to be taken that such efforts don't end up unnecessarily exposing users to risk, King said. “There's a fine line between public service and a publicity stunt.”