Incident: Unauthorized Access to Women's Digital Accounts via Password Breaking Software

Published Date: 2019-07-12

Postmortem Analysis
Timeline 1. The software failure incident involving unauthorized access to women's digital accounts by Justin Potts using Elcomsoft Phone Breaker software happened between March 2015 and December 2016 [Article 87194].
System 1. Elcomsoft Phone Breaker software [87194]
Responsible Organization 1. Justin Potts - The individual gained unauthorized access to women's digital accounts using password breaking software [Article 87194].
Impacted Organization 1. More than 100 women's digital accounts were impacted by the software failure incident [Article 87194].
Software Causes 1. The software cause of the failure incident was the unauthorized use of Elcomsoft Phone Breaker software by Justin Potts to gain access to the women's online accounts [87194].
Non-software Causes 1. Lack of proper security measures in place to prevent unauthorized access to digital accounts [Article 87194] 2. Failure of individuals to use strong and unique passwords for their online accounts [Article 87194] 3. Insufficient awareness and education on cybersecurity best practices among the affected individuals [Article 87194]
Impacts 1. Personal information and photographs of over 100 women were accessed without permission [87194]. 2. The unauthorized access led to the saving of personal information of the women on the perpetrator's electronic devices [87194]. 3. The incident resulted in a criminal conviction for the perpetrator, who was sentenced to three years' probation [87194].
Preventions 1. Implementing multi-factor authentication for the online accounts could have prevented unauthorized access even if the passwords were compromised [87194]. 2. Regularly updating and patching software vulnerabilities could have prevented the exploitation of software weaknesses by individuals like Justin Potts [87194]. 3. Conducting security awareness training for users to prevent falling victim to phishing attacks or social engineering tactics that could lead to unauthorized access [87194].
Fixes 1. Implementing stricter user authentication measures to prevent unauthorized access [87194] 2. Enhancing security protocols to detect and prevent password-breaking software usage [87194] 3. Conducting regular security audits and monitoring for unusual account access patterns [87194]
References 1. Statement from Assistant U.S. Attorney Melissa M. Marangola [Article 87194] 2. Report in the Rochester Democrat and Chronicle [Article 87194] 3. Elcomsoft's website [Article 87194] 4. Elcomsoft spokesperson as quoted by Fox News [Article 87194] 5. Department of Justice U.S. Attorney’s Office Western District of New York [Article 87194] 6. Rochester police [Article 87194] 7. FBI’s Cyber Task Force [Article 87194] 8. U.S. District Judge Charles J. Siragusa [Article 87194]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to unauthorized access to digital accounts using Elcomsoft Phone Breaker software happened with the same software at one_organization, as mentioned in the article [87194]. Justin Potts gained unauthorized access to more than 100 women's digital accounts using the Elcomsoft Phone Breaker software between March 2015 and December 2016. The software was used to harvest usernames and passwords of online accounts, including Facebook, iCloud, Gmail, Yahoo, and Hotmail accounts. (b) The incident involving unauthorized access to digital accounts using Elcomsoft Phone Breaker software could potentially be considered a software failure that has happened at multiple_organization, as the software was mentioned to be used by bad actors for unauthorized access. The Elcomsoft spokesperson acknowledged that their software is sometimes used by bad people for unauthorized purposes, such as breaking into someone else's account, which is a violation of their software agreement.
Phase (Design/Operation) design, operation (a) The software failure incident in the article can be attributed to the design phase. The incident occurred because the individual, Justin Potts, used Elcomsoft Phone Breaker software, which is designed for forensic access to information stored in Apple devices, to gain unauthorized access to more than 100 women's digital accounts [87194]. This software, although intended for law enforcement agencies, was misused by Potts for unauthorized access, highlighting a failure in the design aspect where the software was exploited for malicious purposes.
Boundary (Internal/External) within_system (a) within_system: The software failure incident in this case was primarily within the system. The failure occurred due to Justin Potts using Elcomsoft Phone Breaker software to gain unauthorized access to women's digital accounts by harvesting usernames and passwords [87194]. Potts exploited the software's capabilities to break into encrypted backups, obtain and analyze backups, synchronized data, and passwords from Apple iCloud [87194]. The misuse of the software by Potts for unauthorized access to various online accounts was a contributing factor originating from within the system itself.
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in this case was primarily due to non-human actions. The incident occurred because the perpetrator, Justin Potts, used Elcomsoft Phone Breaker software, a tool designed for forensic access to information stored in Apple devices, to gain unauthorized access to more than 100 women's digital accounts [87194]. The software itself was not designed for malicious purposes but was misused by Potts to harvest usernames and passwords, leading to the security breach. (b) Human actions also played a significant role in this software failure incident. Justin Potts, through his deliberate actions, utilized computer knowhow and password-breaking software to access the accounts without permission. His intentional misuse of the software and his unauthorized access to the accounts demonstrate the critical role of human actions in causing this security breach [87194].
Dimension (Hardware/Software) software (a) The software failure incident in this case was not due to hardware issues but rather due to contributing factors that originated in software. The incident involved the unauthorized access to women's digital accounts by Justin Potts using computer knowhow and password breaking software like Elcomsoft Phone Breaker [87194]. The software allowed Potts to gain access to accounts such as Facebook, iCloud, Gmail, Yahoo, and Hotmail without permission of the owners, indicating a software-related failure.
Objective (Malicious/Non-malicious) malicious (a) The software failure incident in this case is malicious. Justin Potts gained unauthorized access to more than 100 women's digital accounts by using computer knowhow and password breaking software [87194]. He accessed accounts like Facebook, iCloud, Gmail, Yahoo, and Hotmail without permission and obtained personal information and photographs of the women [87194]. Potts saved this personal information on his electronic devices, indicating a clear intent to harm the system and violate the privacy of the account owners. Additionally, the software used by Potts, Elcomsoft Phone Breaker, is primarily intended for forensic access to information stored in Apple devices for law enforcement agencies, but it was misused in this case for malicious purposes [87194].
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident: The software failure incident in this case falls under the category of poor_decisions. The incident involved a man named Justin Potts who gained unauthorized access to over 100 women's digital accounts using password-breaking software. Despite the software being intended for forensic purposes for law enforcement agencies, it was misused by Potts for illegal activities, violating the software agreement. The software company acknowledged that their software was being used by bad people for bad purposes, indicating a failure due to poor decisions made by the individual misusing the software [87194].
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident in Article 87194 can be attributed to development incompetence. The incident involved a man named Justin Potts gaining unauthorized access to women's digital accounts by using computer knowhow and password breaking software, specifically Elcomsoft Phone Breaker. The software, designed for forensic access to information stored in Apple devices, was misused by Potts to harvest usernames and passwords, indicating a lack of professional competence in ensuring the software's ethical use [87194]. (b) Additionally, the incident can also be categorized as accidental, as the Elcomsoft spokesperson mentioned that their software is sometimes used by bad actors for unauthorized purposes like breaking into someone else's account, which is a violation of their software agreement. The spokesperson acknowledged that while their software is primarily intended for Law Enforcement Agencies, they have limited control over preventing its misuse by individuals like Potts, indicating an accidental aspect to the misuse of the software [87194].
Duration temporary The software failure incident described in the article is more aligned with a temporary failure. The incident involving Justin Potts gaining unauthorized access to women's digital accounts through the use of Elcomsoft Phone Breaker software occurred between March 2015 and December 2016 [Article 87194]. This indicates that the unauthorized access and breach of accounts were limited to a specific time frame, making it a temporary software failure incident.
Behaviour value, other (a) crash: The software failure incident in the article does not involve a crash where the system loses state and does not perform any of its intended functions [87194]. (b) omission: The software failure incident does not involve omission where the system omits to perform its intended functions at an instance(s) [87194]. (c) timing: The software failure incident does not involve timing issues where the system performs its intended functions correctly, but too late or too early [87194]. (d) value: The software failure incident involves a value issue where the system performs its intended functions incorrectly. In this case, the software was used by an individual for unauthorized access to women's digital accounts, violating the software agreement [87194]. (e) byzantine: The software failure incident does not involve a byzantine behavior where the system behaves erroneously with inconsistent responses and interactions [87194]. (f) other: The other behavior in this software failure incident is unauthorized access and misuse of the software for illegal activities, specifically breaking into someone else's accounts [87194].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property (d) property: People's material goods, money, or data was impacted due to the software failure The consequence of the software failure incident in this case was related to property. The unauthorized access gained by Justin Potts to more than 100 women's digital accounts, including Facebook, iCloud, Gmail, Yahoo, and Hotmail accounts, resulted in him obtaining their personal information and personal photographs without permission. He then saved this personal information on his electronic devices [87194].
Domain information (a) The failed system in this incident was related to the industry of information, specifically the unauthorized access to women's digital accounts such as Facebook, iCloud, Gmail, Yahoo, and Hotmail accounts [Article 87194].

Sources

Back to List