Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Week 2 Presentation Proposal #2382

Merged
merged 1 commit into from
Aug 30, 2024
Merged

Week 2 Presentation Proposal #2382

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions contributions/presentation/week2/ghenn-vikfor/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Assignment Proposal

## Title

The Crowdstrike bug, and the importance of high-quality testing

## Names and KTH ID

- Gustav Henningsson ([email protected])
- Viktor Fornstad ([email protected])

## Deadline

- Week 2

## Category

- Presentation

## 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.
Loading