Failures Database
This database contains reports analyzing software failures from the news. Currently, it contains failures from 2010 to 2022. This database was created through the FAIL (Failure Analysis Investigation with LLM) project. FAIL leverages Large Language Models (LLMs) to collect and analyze software failures reported in the news. Our work has been presented in the paper titled "FAIL: Analyzing Software Failures from the News Using LLMs." Contributing members include Dharun Anandayuvaraj, Matthew Campbell, Tanmay Singla, Parth Patil, Arav Tewari, and James C. Davis from Purdue University.
| Title | Published Date | System | Number of Articles | Actions |
|---|---|---|---|---|
| Cyber Attacks Targeting Middle East Energy Companies. | 2012-08-31 | The software failure incident mentioned in the article is related to malware attacks targeting organizations in the Middle East. The systems that failed in this incident are: 1. Corporate networks and websites of energy companies in the Middle East, such as Qatari liquified natural gas producer RasGas and Saudi Aramco oil company [14080]. | 1 | View Details |
| Twitter Security Vulnerability Allows Account Hijacking via Brute Force. | 2012-10-01 | 1. Twitter's password reset process 2. Security system that limits log-in attempts by IP address 3. Lack of two-factor authentication 4. Vulnerability to brute force attacks | 1 | View Details |
| Watson AI Swearing Incident: Urban Dictionary Download Gone Wrong | 2013-01-12 | 1. IBM supercomputer Watson 2. Urban Dictionary repository 3. Linguistic filter developed by Mr. Brown's team [16208] | 1 | View Details |
| iCloud Glitch Extends Storage Renewal Dates to 2050 | 2012-09-30 | The system that failed in the software failure incident described in Article 14695 is: 1. iCloud account system [14695] | 1 | View Details |
| Firefox 16 Security Vulnerability: Immediate Patch Released by Mozilla | 2012-10-11 | 1. Firefox 16 [15177] | 1 | View Details |
| 'Hackers Crack 16-Character Passwords in Less Than an Hour' | 2013-05-28 | The software failure incident described in the article was primarily due to weaknesses in the password hashing and security systems. The systems that failed in this incident include: 1. Password hashing system: The hashing system used to store passwords failed to adequately protect the passwords, allowing hackers to crack a significant number of hashed passwords [18962]. 2. Cryptographic salt implementation: The use of cryptographic salt to enhance password security failed to prevent the cracking of passwords, indicating potential weaknesses in the salt generation or application [18962]. 3. Password complexity and strength enforcement: The incident revealed weaknesses in enforcing password complexity and strength requirements, as even 16-character passwords were cracked easily [18962]. 4. Brute-force attack vulnerability: The system was vulnerable to brute-force attacks, allowing hackers to systematically try all possible combinations of characters to crack passwords [18962]. 5. Lack of robust password policies: The incident highlighted potential shortcomings in the password policies and practices employed by the system, leading to the successful cracking of a large number of passwords [18962]. Overall, the failure of these systems and components contributed to the security breach and the successful cracking of a significant number of passwords by hackers. | 1 | View Details |
| Cybersecurity Breach at New York Times by Chinese Hackers | 2013-01-31 | 1. Antivirus products made by Symantec [16391] 2. Monitoring software that identified and quarantined only one of the attacker's tools [16391] | 1 | View Details |
| Windows RT Hack Allows Running Unsigned Desktop Apps | 2013-01-08 | 1. Windows RT operating system [16442] | 1 | View Details |
| iOS 6 "Do Not Disturb" Bug Causes New Year's Day Alarm Failures | 2013-01-02 | 1. iOS 6's "Do Not Disturb" feature [16452] | 1 | View Details |
| Vodafone BlackBerry Outage: Data Services Disrupted in Europe, MEA | 2013-01-11 | The system that failed in the software failure incident reported in Article 16579 was: 1. Vodafone's network due to a router error [16579]. | 1 | View Details |