DEV Community

Discussion on: Log4j 2: New vulnerability on DoS in 2.16.0 and below

Collapse
 
cubikca profile image
Brian Richardson

Unfortunately there's no way of knowing if a third-party vendor has a weird logging configuration and a vulnerable version of Log4j. This makes update #3 now. My company's approach was to block the payload protocols to external hosts first, then focus on finding and patching. This has worked well for us: all logged attempts were blocked and would have used LDAP anyway, which was blocked.

Collapse
 
nabbisen profile image
nabbisen

Exactly. It's available to detect Log4j version and configuration and also update it only when you are able to own it or at least customize.

Thank you for sharing knowledge and effort of your company😃