Just submitted @OpenJDK enhancement request (#9076208) to define an allow list of CIDR addresses for creating outbound network connections. This would provide immediate mitigation for an entire class of exploits that target Java-based systems.
@omniprof So our 'best practice' reads-- synchronized is fine for anything that stays JVM-only-- working with caches & collections, logic code, etc. Anytime something leaves the JDK (disk IO, network IO, etc) then have a recoverable block of code using a lock instead.
@omniprof synchronized doesn't have a timeout so the trade-off of convenience when using it is YOLO if the block inside does anything external to the JVM
If you still have Log4j questions, especially surrounding Apache ActiveMQ, you'll want to check out this security bulletin from HYTE. #log4j#log4shell#activemq
https://t.co/XWO74tANtb
HYTE Technologies, Inc. latest information on Log4Shell information and impacts to HYTE MQ and Apache ActiveMQ
#log4shell#activemq#hytemq
https://t.co/uwlIlSAM6v
@brunoborges@Veracode Agreed, upgrade the the recommended and long-term approach. There are situations where upgrading 1k's and 10k's of remote devices is higher risk and requires a longer test & verify process than setting a property and restarting.