An unknown number of users encountered a blank screen after rearranging elements in various tables and attempting to access some of those elements. The issue started on UTC-5 23-09-06 13:21 and was proactively discovered 1.9 days (TTD) later by one of our developers who reported through our help desk [1] that a blank screen appeared when rearranging elements in the vulnerability table and then attempting to access one of the vulnerabilities. The problem was resolved in 6.7 hours (TTF), resulting in a total window of exposure of 2.1 days (WOE) [2].
To persist sorting preferences, the hook useStoredState was utilized. For proper functionality, this hook requires the use of the useState function, which was inadvertently omitted. As a result, the value was updated correctly, causing preferences set in one table to be applied globally instead of separately for each table. Consequently, when switching between tables, instructions were passed for attributes that existed in the first table but not in the second, leading to an error that triggered the blank screen [3].
The persistence of sorting preferences was disabled, preventing the saving of sorting options and mitigating the issue [4].
While the platform had tests confirming correct sorting in tables, these tests did not account for a sorting persistence feature that was newly introduced. Consequently, no tests were added for this feature, nor were they effectively tested manually upon implementation. MISSING_TEST