dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Jul 2024.
Jai ExtApplication · Geosolutionsgroup

CVE-2022-24816

CRITICAL · 10.0 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 1.1.22 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
JAI-EXT is an open-source project which aims to extend the Java Advanced Imaging (JAI) API. Programs allowing Jiffle script to be provided via network request can lead 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. Version 1.2.22 will contain a patch that disables the ability to inject malicious code into the resulting script. Users unable to upgrade may negate the ability to compile Jiffle scripts from the final application, by removing janino-x.y.z.jar from the classpath.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JAI-EXT allows Jiffle scripts to be compiled into Java code via the Janino compiler. When Jiffle scripts can be provided via network requests (as in GeoServer), attackers can inject malicious Java code into the script that gets compiled and executed server-side, resulting in unauthenticated Remote Code Execution.

MitigationUpgrade to JAI-EXT version 1.2.22 or later which patches the vulnerability. If upgrading is not possible, remove janino-x.y.z.jar from the classpath to prevent Jiffle script compilation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jai ExtApplication
Affected:< 1.1.22

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JAI-EXT version
    Locate the jai-ext library JAR in your application's classpath or dependencies and inspect its version. Common locations: WEB-INF/lib, lib/, or check your dependency management file (pom.xml, build.gradle).
    Affected if The installed version is lower than 1.1.22 (for example, 1.1.21, 1.1.20, or any 1.0.x release).
  2. Confirm Jiffle scripting is in use
    Search your application logs, code, or configuration for references to Jiffle, especially any endpoints or services that accept script input. Look for classes like net.algart.jiffle.Jiffle or usage of JiffleRuntime. Check if your application exposes functionality that processes Jiffle scripts.
    Affected if Your application processes Jiffle scripts, particularly from untrusted network sources.
  3. Check for Janino compiler presence
    Search the classpath for janino JAR files (janino-*.jar, commons-compiler-*.jar). These are required for Jiffle script compilation. Check WEB-INF/lib, lib/, or list all JARs in your runtime classpath.
    Affected if The janino JAR is present on the classpath, which enables Jiffle script compilation.
  4. Identify network-exposable Jiffle endpoints
    Review your application's web endpoints, REST APIs, or any network-accessible services that accept script content. Look for parameters or request bodies that could contain Jiffle script code. Check GeoServer's WPS (Web Processing Service) or any custom endpoints using JAI-EXT.
    Affected if Jiffle script input can be received over the network from users or external systems.

You are affected if JAI-EXT version is below 1.1.22 AND the Janino compiler is on the classpath AND your application accepts Jiffle scripts from network sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.22 or later
Fixed in 1.1.22
Vendor patch github.com →
Interim mitigation

Upgrade to JAI-EXT version 1.2.22 or later which patches the vulnerability. If upgrading is not possible, remove janino-x.y.z.jar from the classpath to prevent Jiffle script compilation.

Recommended fix High confidence

JAI-EXT version 1.2.22 or later

  1. Upgrade JAI-EXT to version 1.2.22 or later, which contains the security patch that disables malicious code injection in Jiffle scripts
  2. If upgrading is not immediately possible, remove janino-x.y.z.jar from the application classpath to prevent Jiffle script compilation and mitigate the RCE vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jai Ext Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24816 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data