Threats / OSGeo / CVE-2022-24816
CVE-2022-24816
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
OSGeo JAI-EXT vulnerability
OSGeo JAI-EXT contains a code injection vulnerability in jt-jiffle that allows remote code execution when Jiffle scripts are accepted from network requests.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject arbitrary code through Jiffle script parameters, achieving remote code execution on systems running vulnerable JAI-EXT deployments. Active exploitation in the wild increases risk.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
731 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-26).
Probability (EPSS)
EPSS 0.98684 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: OSGeo, JAI-EXT. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Jiffle script and send it via network request to an application using jt-jiffle.
Business
The application processes untrusted script input without validation, creating an execution pathway.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject code that executes during Jiffle script compilation or interpretation.
Business
The vulnerability allows code execution in the context of the application process.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain remote code execution with the privileges of the vulnerable application.
Business
Attackers can compromise system integrity, steal data, or establish persistence on affected infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05