CVE-2022-24816

Improper Control of Generation of Code ('Code Injection') in jai-ext

Workarounds

Negate the ability to compile Jiffle scripts from the final application, by removing janino-x.y.z.jar from the classpath.

References

None.

Programs using jt-jiffle, and allowing Jiffle script to be provided via network request, are susceptible to a Remote Code Execution as the Jiffle script is compiled into Java code via Janino, and executed. In particular, this affects the downstream GeoServer project.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2022-24816 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.22); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Version 1.2.22 will contain a patch that disables the ability to inject malicious code into the resulting script.

1. What is CVE-2022-24816? CVE-2022-24816 is a critical-severity code injection vulnerability in it.geosolutions.jaiext.jiffle:jt-jiffle (maven), affecting versions < 1.1.22. It is fixed in 1.1.22. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2022-24816? CVE-2022-24816 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-24816?
   • it.geosolutions.jaiext.jiffle:jt-jiffle (maven) (versions < 1.1.22)
   • it.geosolutions.jaiext.jiffle:jt-jiffle-language (maven) (versions < 1.1.22)
4. Is there a fix for CVE-2022-24816? Yes. CVE-2022-24816 is fixed in 1.1.22. Upgrade to this version or later.
5. Is CVE-2022-24816 exploitable, and should I be worried? Whether CVE-2022-24816 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
6. What actually determines whether CVE-2022-24816 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.
7. How do I fix CVE-2022-24816?
   • Upgrade it.geosolutions.jaiext.jiffle:jt-jiffle to 1.1.22 or later
   • Upgrade it.geosolutions.jaiext.jiffle:jt-jiffle-language to 1.1.22 or later