Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

GeoServer/JAI-EXT Jiffle (Janino) code injection RCE

IdentifiersCVE-2022-24816CWE-94· Improper Control of Generation of…

JAI-EXT jt-jiffle (used downstream by GeoServer) allows code injection when an application accepts untrusted Jiffle scripts (e.g., via network requests). Jiffle scripts are translated into Java source and then compiled/executed via the Janino compiler; insufficient restriction of what can be emitted into the generated Java enables an attacker to inject malicious Java constructs and reach dangerous APIs (e.g., java.lang.Runtime.getRuntime().exec), resulting in remote code execution in affected GeoServer configurations.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote, potentially unauthenticated code execution on the GeoServer host in configurations where attacker-controlled Jiffle can be supplied (noted paths include crafted OGC/WPS requests such as wps:Execute with wps:LiteralData; also potentially via SLD rendering transformations and admin-console SLD editing depending on deployment). Successful exploitation yields arbitrary command execution with the privileges of the GeoServer process.

Mitigation

If you can’t patch tonight, do this now.

If upgrade is not immediately possible, disable Jiffle compilation by removing the Janino JAR (janino-<version>.jar) from the application classpath (e.g., from GeoServer WAR WEB-INF/lib) and restart. Additionally, ensure the application does not accept Jiffle scripts from untrusted/network sources.

Remediation

Patch, then assume compromise.

Upgrade to a fixed release of the affected components. The provided content indicates a patch in JAI-EXT 1.2.22 that disables malicious code injection into the generated script; another advisory notes fixed GeoServer components/artifacts in 2.18.6 and fixed jt-jiffle packages at >= 1.1.22 (and references 1.2.22 as patched as well).
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2022-24816MaturityPoCVerified exploit

This repository provides a Python exploit script (CVE-2022-24816.py) targeting the GeoServer software vulnerable to CVE-2022-24816, a remote code execution (RCE) vulnerability. The exploit works by sending a specially crafted XML payload to the /geoserver/wms endpoint, abusing the WPS Execute functionality to inject Java code that executes arbitrary system commands on the server. The script takes two arguments: the target GeoServer URL and the command to execute. It processes the server's XML response to extract and display the output of the executed command. The repository includes a README with usage instructions, a requirements.txt listing Python dependencies (requests, urllib3, colorama), and a LICENSE file. The exploit is operational, allowing attackers to run arbitrary commands on vulnerable GeoServer instances accessible over the network.

c1ph3rbyt3Disclosed Jan 17, 2025pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GeosolutionsgroupJai-Extapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.