Summary
QOS.CH logback-core Expression Language Injection vulnerability
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core up to and including version 1.5.12 in Java applications allows attackers to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution.
Malicious logback configuration files can allow the attacker to execute arbitrary code using the JaninoEventEvaluator extension.
A successful attack requires the user to have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privilege.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
ch.qos.logback:logback-core to 1.5.13 or later; ch.qos.logback:logback-core to 1.3.15 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-12798? CVE-2024-12798 is a medium-severity security vulnerability in ch.qos.logback:logback-core (maven), affecting versions >= 1.4.0, < 1.5.13. It is fixed in 1.5.13, 1.3.15.
- Which versions of ch.qos.logback:logback-core are affected by CVE-2024-12798? ch.qos.logback:logback-core (maven) versions >= 1.4.0, < 1.5.13 is affected.
- Is there a fix for CVE-2024-12798? Yes. CVE-2024-12798 is fixed in 1.5.13, 1.3.15. Upgrade to this version or later.
- Is CVE-2024-12798 exploitable, and should I be worried? Whether CVE-2024-12798 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-12798 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-12798?
- Upgrade
ch.qos.logback:logback-coreto 1.5.13 or later - Upgrade
ch.qos.logback:logback-coreto 1.3.15 or later
- Upgrade