Bugcrowd’s Log4j Response: Behind the Numbers
bugcrowd.com | research | #rce | #vulnerability-management | #incident-response | #log4j | #bugcrowd | #triage | #log4shell
Summary
Bugcrowd processed 1,200+ raw Log4j reports, validating over 500 for customers. Submissions peaked December 11 at nearly 300; most P1s were validated and triaged in under three hours.
- Published
- Collected
--- id: 887 title: "Bugcrowd’s Log4j Response: Behind the Numbers" source_domain: bugcrowd.com source_url: "https://www.bugcrowd.com/blog/bugcrowds-log4j-response-behind-the-numbers/" published_at: "2022-01-06 00:00" tags: ["rce", "vulnerability-management", "incident-response", "log4j", "bugcrowd", "triage", "log4shell"] phying_url: "https://phying.com/item/887" lang: en --- # Bugcrowd’s Log4j Response: Behind the Numbers ## Summary Bugcrowd processed 1,200+ raw Log4j reports, validating over 500 for customers. Submissions peaked December 11 at nearly 300; most P1s were validated and triaged in under three hours. ## Intelligence Metadata - **Sources:** bugcrowd.com - **Published:** 2022-01-06 00:00 - **Original:** https://www.bugcrowd.com/blog/bugcrowds-log4j-response-behind-the-numbers/ - **Phying News:** https://phying.com/item/887