Skip to content
Fencer Intel
medium 5.9

CVE-2024-12798 json

JaninoEventEvaluator vulnerability

published last yr. modified 2mo ago also GHSA-pr98-23f8-jwxv , EUVD-2024-3605

cvss
5.9
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core upto including version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications allows attacker 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.

Patch / fix

  • maven ch.qos.logback:logback-core 1.3.15, 1.5.13
  • QOS.CH Sarl Logback-core 1.3.15, 1.5.13
  • logback Debian 14 1:1.6.3-1

debian advisories DEBIAN-CVE-2024-12798

  • xmvn SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 4.3.0-150200.3.33.1
  • maven SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 3.10.0-150200.4.36.1
  • slf4j SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7, SLE High Performance Computing 15 SP5-ESPOS +9 more 2.0.20-150200.3.7.1
  • jline3 SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 3.30.17-150200.5.11.1
  • methanol SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 1.9.0-150200.5.3.1
  • aqute-bnd SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 6.4.1-150200.3.16.1
  • xmvn-mojo SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 4.3.0-150200.3.33.1
  • xmvn-tools SLE Module for Development Tools 15 SP7, SLE High Performance Computing 15 SP5-ESPOS, SLE High Performance Computing 15 SP4-ESPOS +8 more 4.3.0-150200.3.33.1

suse advisories SUSE-SU-2026:5189-1SUSE-SU-2025:0072-1

  • logback openSUSE Tumbleweed 1.2.11-4.1

opensuse advisories openSUSE-SU-2025:14627-1

Is CVE-2024-12798 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-12798 updated cvss 5.5

logback-core: arbitrary code execution via JaninoEventEvaluator

  • Red Hat A-MQ Clients 2 logback-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Logging Subsystem for Red Hat OpenShift logback-core Red Hat AMQ Broker 7 logback-core
    affected: workaround, no fix available
  • Red Hat AMQ Clients logback-core Red Hat build of Apache Camel - HawtIO 4 logback-core
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Debezium 2 logback-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of OptaPlanner 8 logback-core Red Hat Ceph Storage 9 libarrow, parquet-libs
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Data Grid 8 logback-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Fuse 7 logback-core Red Hat Integration Camel K 1 logback-core Red Hat JBoss Data Grid 7 logback-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Process Automation 7 logback-core
    affected: workaround, no fix available “Fix deferred”
show 6 more
  • Red Hat Single Sign-On 7 logback-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat streams for Apache Kafka logback-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat streams for Apache Kafka 3 logback-core
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Apache Camel 4.8.3 for Spring Boot
    fixed: vendor fix RHSA-2025:1078
  • Red Hat Build of Keycloak logback-core
    not affected: component not present
  • Red Hat JBoss Enterprise Application Platform 7 logback-core Red Hat JBoss Enterprise Application Platform 8 logback-core Red Hat JBoss Enterprise Application Platform Expansion Pack logback-core Red Hat JBoss Web Server 6 logback-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 4.0 5.9 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/RE:L/U:Clear
CNA 4.0 5.9 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:L/U:Clear

Affected packages

ecosystem package affected fixed in
maven ch.qos.logback:logback-core
>=1.4.0, <1.5.13
<1.3.15
1.5.13
1.3.15

Affected products

  • QOS.CH Sarl Logback-core

Classification

Weakness
  • CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.