Real Enterprise Java developer are probably still using log4j 1.x so are unaffected by the bug.