Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity

Better heading sizes (#24401)

Browse Source
This commit is contained in:
Luke Heath
2024-12-04 17:24:12 -05:00
committed by GitHub
parent 8bf7afb433
commit e479ddce42
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/resolving-a-critical-firefox-vulnerability-using-fleets-new-automation-features.md
+2 -2
View File
@@ -6,7 +6,7 @@ When Mozilla announced a critical vulnerability in Firefox ([CVE-2024-115](https
The vulnerability, as detailed in a [CISecurity advisory](https://www.cisecurity.org/advisory/a-vulnerability-in-mozilla-firefox-could-allow-for-arbitrary-code-execution_2024-115), could allow attackers to execute arbitrary code on devices running an outdated version of Firefox. Addressing this swiftly was essential to maintain security and compliance across all endpoints.
### Automating the response with Fleet
## Automating the response with Fleet
Fleet recently introduced a feature that allows users to automatically install or upgrade software on policy failure. This capability, outlined in our [guide on automatic software installation](https://fleetdm.com/guides/automatic-software-install-in-fleet), became the basis of our solution.
@@ -46,7 +46,7 @@ With this policy in place, Fleet automatically identified devices running an out
Before deploying the policy, we identified over a dozen devices running vulnerable versions of Firefox. After merging the policy changes, Fleet’s automation took over. By the next morning, every affected device had been seamlessly updated to the secure version 132.0—all without any manual intervention or disruption to end users.
### Why This matters
## Why This matters
This experience underscores the power and agility of Fleet’s new automation features: