Skip to content

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

Critical severity GitHub Reviewed Published Apr 13, 2022 in geosolutions-it/jai-ext • Updated Sep 19, 2023

Package

maven it.geosolutions.jaiext.jiffle:jt-jiffle (Maven)

Affected versions

< 1.1.22

Patched versions

1.1.22
maven it.geosolutions.jaiext.jiffle:jt-jiffle-language (Maven)
< 1.1.22
1.1.22

Description

Impact

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.

Patches

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

Workarounds

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

References

None.

References

@aaime aaime published to geosolutions-it/jai-ext Apr 13, 2022
Published by the National Vulnerability Database Apr 13, 2022
Published to the GitHub Advisory Database Sep 19, 2023
Reviewed Sep 19, 2023
Last updated Sep 19, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

96.672%
(100th percentile)

Weaknesses

CVE ID

CVE-2022-24816

GHSA ID

GHSA-v92f-jx6p-73rx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.