How to fix a bug in a fix
Project Zero collaborates with software companies to fix reported vulnerabilities and provides advice on increasing software security. Some vendors worry about their inability to patch vulnerabilities that immediately harm users due to patch delivery system constraints. Project Zero shares its findings from discussions with large vendors and security reviews.
It highlights systems that help vendors remediate small numbers of vulnerabilities faster than typical update processes. These systems aim to give vendors a reference for enhancing capabilities and encourage them to prepare for urgent vulnerabilities before they arise. Patching typically includes several stages, but this is a simplified view.
Additional steps may occur due to test failures or third-party involvement. However, triage and patch development time significantly impact emergency patching speed. Vendors know they face urgent problems, so triage is usually fast, and patch development can be prioritized. Rarely, delays occur due to complex vulnerabilities or incomplete software component knowledge.
Emergency updates are limited by testing and delivery stages. Testing is crucial to prevent unexpected software behavior, such as rendering devices unusable or corrupting data. The cost of poorly tested updates varies by software type. For instance, a malfunctioning mobile app can be replaced via an app store, while a bricked device may need repair, causing significant costs.
Technical challenges also affect patch delivery speed, including patching system design, user interaction requirements, and network constraints. Feature flags, used for temporary vulnerability fixes, can expedite updates by allowing testing with each flag setting. This method enables rapid updates with less testing, as users can quickly revert to a previous version if issues arise.
Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.