Log4shell, Is It Apache Foundation's Fault?
summary
A retrospective on the Log4J/Log4Shell incident covering its history, technical root causes, and the fixes applied. It examines effects on internal and external projects and presents a post-mortem, including how Apache handles CVEs, weaknesses in code review and project governance, and options to prevent future incidents (funding, organization, mandatory audits), plus reactions from affected companies and governments.
AI-written summary · about
chapters (5)
- 0:00Log4Shell intro
- 10:19Log4j origins
- 27:37Apache security process
- 38:06Post-Log4Shell fixes
- 44:25Conclusion
related talks
27mLog4Shell - The Open Source World on Fire
51mDouble plus Ungood Why Log4Shell Is So Bad
33mLog4J, SpringShell and all that Jazz (or why bad things can happen to good software)
51mLog4Shell Armageddon or Opportunity
17mLog4j - A Placement Student's Baptism by Fire
25mDevSecOps by Default: What have, can and must we learn from Log4Shell?
58mWhat the log4j incident taught us about Secure by Design
40mWhat Log4j taught me
