Conversation
javierron
added
proposal
Collaborator
|
@GustavHenningsson Thanks for the proposal. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
The Crowdstrike bug, and the importance of high-quality testing
Names and KTH ID
Deadline
Category
Description
We want to take a look at the Crowdstrike bug that happened in July of this year.
Crowdstrike is a company that sells anti-malware services, endpoint protection software, and threat-intelligence services.
On the 19th of July 2024, a new version of one of their softwares caused over 8 million Windows computers to crash, due to a array out-of-bounds memory exception.
This was not caught in any of the testing done by Crowdstrike prior to deployment. The tests used Regular Expressions, and wildcard matching that missed the oob-exception every time.
Since the software in question is running in kernel level 0, this was catastrophic for the computer, and caused an system-wide crash.
We will look at how the automated testing failed, aswell as what Crowdstrike have done(or could have done) to fix it.
Relevance
The bug in the update should have been caught by the automated testing Crowdstrike ran before deployment.
However, due to the way that the tests were set up, this issue slipped through all tests and made it to live.
This issue higlights the importance of not only having tests, but writing good tests. Just because your commit passes all tests does not mean that it's 100 procent safe.