Impact
At least one user experienced issues accessing db.fluidattacks.com, which was not loading correctly in the browser. The issue started on UTC-5 26-03-06 21:48 and was proactively discovered 2.5 days (TTD) later by a staff member who noticed that the application failed to render properly due to blocked resources, making the platform unusable. The problem was resolved in 2.4 hours (TTF), resulting in a total window of exposure of 2.6 days (WOE) [1].
Cause
The issue was caused by an incompatibility between a newly implemented caching mechanism and the existing Content Security Policy (CSP) headers. While the change worked correctly in the local environment, differences between local and production environments (specifically CSP enforcement) caused resources to be blocked in production, preventing proper rendering [2].
Solution
The change was reverted to restore normal operation of the DB. After stabilizing the platform, the caching implementation approach was revised to ensure compatibility with the CSP configuration before being reintroduced [3].
Conclusion
This incident highlights the importance of understanding and validating CSP behavior in production environments. Future changes must consider CSP constraints to avoid introducing features that are incompatible with existing security policies. INFRASTRUCTURE_ERROR < INCOMPLETE_PERSPECTIVE