CVE-2022-24816: Code Injection Vulnerability in jt-jiffle

Summary

19/09/2023
Yes i
Critical
9.8

CVE-2022-24816: Improper Control of Generation of Code ('Code Injection') in jai-ext. Affects it.geosolutions.jaiext.jiffle:jt-jiffle versions < 1.1.22. Fixed in 1.1.22. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The jt-jiffle package is a Java library that provides a scripting language for image processing. It is commonly used in applications that require dynamic image manipulation. This vulnerability allows an attacker to inject malicious code into the Jiffle script, which is then compiled and executed, leading to remote code execution. This vulnerability affects versions 0 to 1.1.22 of the jt-jiffle package.

Vulnerability Detail

The vulnerability arises from improper control of code generation in jt-jiffle. When a Jiffle script is provided via a network request, it is compiled into Java code using Janino and then executed. This allows an attacker to inject arbitrary code into the resulting script, leading to remote code execution. This vulnerability is particularly critical for applications that use jt-jiffle and allow Jiffle scripts to be provided externally, such as the GeoServer project.

How To Fix

Minimum fixed version

1.1.22

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating the package is not immediately feasible, a workaround is to remove the janino-x.y.z.jar file from the classpath of the final application. This will negate the ability to compile Jiffle scripts, preventing the exploitation of this vulnerability.

Conclusion

The code injection vulnerability in jt-jiffle allows for remote code execution, posing a significant risk to applications that use Jiffle scripts provided externally. It is crucial to update to version 1.2.22 of the jt-jiffle package or apply the recommended workaround to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for it.geosolutions.jaiext.jiffle:jt-jiffle →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary code remotely, potentially leading to a complete compromise of the affected system. This can result in unauthorized access, data theft, or further exploitation of the compromised system.

Versions 0 to 1.1.22 of the jt-jiffle package are affected by this vulnerability.

Yes, a patch is available in version 1.2.22 of the jt-jiffle package. Updating to this version will mitigate the vulnerability.

Yes, this vulnerability can be exploited remotely. An attacker can provide a malicious Jiffle script via a network request, which will then be compiled and executed on the target system.

There are no known instances of this vulnerability being exploited in the wild at the time of this advisory. However, it is important to apply the patch or workaround to prevent potential exploitation.

How To Fix

Minimum fixed version

1.1.22

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback