This weekExploitable · Confirmed
log4j:log4j, org.zenframework.z8.dependencies.commons:log4j-1.2.17: JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted…
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- log4j:log4j (Maven): from 1.2.0, up to and including 1.2.17
- org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): every version, up to and including 2.0
The fix
No fix yet: isolate it or follow the vendor's mitigation.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at 81%.
FIRST EPSSStated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)