Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


08:30 AM

San Bernardino iPhone Hack Tool Cost FBI ‘Under $1 Million’

Agency now owns mechanism that can exploit unknown Apple security flaws.

The FBI paid under $1 million to the contractor who cracked the iPhone owned by the San Bernardino shooter, according to US government sources who spoke to Reuters.

This is a different figure than the $1.3 million figure FBI director James Comey had suggested last week. When asked how much the third party was paid for the hacking tool, Comey had replied that it was more than what he would make during the rest of his tenure, which is seven years and four months.

The identity of the third party that cracked the iPhone is reportedly a closely-guarded secret: according to the report, Comey does not even know their identity.

The sources told Reuters that although the tool is now owned by the FBI which it could use to unlock other iPhone 5Cs with iOS 9, the agency does not know details of the hacking method.

For more on this story, go to Reuters

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
4/30/2016 | 7:47:56 PM
Since the secrets of the hack cannot be divulged to Apple from the FBI, does Apple have the right to acquiese the identity of the third party since it involves an work around to their hardware, software, and security protocols?
User Rank: Ninja
4/30/2016 | 7:43:53 PM
Relevant Information
Now the question is was the amount of money worth it? Are there any reports currently to support that helpful data was found on the phone or not at this point?
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.