`CVE-2022-37021` Apache Geode

Affected software	Apache Geode
Severity	9.8 Critical CVSS 3.1
Fixed in	`1.12.16`, `1.13.5`, `1.14.1`
Weakness	Deserialization of untrusted data (CWE-502)
Published	31 Aug 2022
Updated	17 Jun 2026

Description

Apache Geode versions up to 1.12.5, 1.13.4 and 1.14.0 are vulnerable to a deserialization of untrusted data flaw when using JMX over RMI on Java 8. Any user still on Java 8 who wishes to protect against deserialization attacks involving JMX or RMI should upgrade to Apache Geode 1.15 and Java 11. If upgrading to Java 11 is not possible, then upgrade to Apache Geode 1.15 and specify "--J=-Dgeode.enableGlobalSerialFilter=true" when starting any Locators or Servers. Follow the documentation for details on specifying any user classes that may be serialized/deserialized with the "serializable-object-filter" configuration option. Using a global serial filter will impact performance.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 4 years ago.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS 2.6% chance in 30 days

Waratek protection

Protected by Waratek

Waratek has a rule that blocks attacks on this vulnerability.

Protection full Deserialization, Process
Action available security rule
Review automated Inferred
Record active

Decided by	A vulnerability class already blocked by an ARMR security rule
Finding	Protected by Waratek's ARMR deserialization security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-502: Deserialization of Untrusted Data.

Decided by

A vulnerability class already blocked by an ARMR security rule

Finding

Protected by Waratek's ARMR deserialization security rule, which blocks this class of attack at the JVM level without a rule written for this CVE specifically. The CVE's weakness is CWE-502: Deserialization of Untrusted Data.

How to mitigate CVE-2022-37021

Upgrade Apache Geode to a release that fixes it: 1.12.16, 1.13.5 or 1.14.1. Until you can, Waratek RASP blocks exploitation with its deserialization and process rules. It runs inside the Java application, with no code changes.

Waratek RASP Runtime protection for Java applications

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.apache.geode:geode-core 0 1.12.16 unbounded

org.apache.geode:geode-core 1.13.0 1.13.5 unbounded

org.apache.geode:geode-core 1.14.0 1.14.1 unbounded

Package	Introduced	Fixed	Last affected
`org.apache.geode:geode-core`	0	`1.12.16`	unbounded
`org.apache.geode:geode-core`	1.13.0	`1.13.5`	unbounded
`org.apache.geode:geode-core`	1.14.0	`1.14.1`	unbounded

Products and versions

2 products, 6 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	apache	geode	generic	≤ 1.12.5 · ≥ 1.13.0 and ≤ 1.13.4 · 1.14.0
osv	org.apache.geode	geode-core	generic	＜ 1.12.16 · ≥ 1.13.0 and ＜ 1.13.5 · ≥ 1.14.0 and ＜ 1.14.1

Source

Vendor

Product

Scheme

Affected versions

nvd

apache

geode

generic

≤ 1.12.5 · ≥ 1.13.0 and ≤ 1.13.4 · 1.14.0

osv

org.apache.geode

geode-core

generic

＜ 1.12.16 · ≥ 1.13.0 and ＜ 1.13.5 · ≥ 1.14.0 and ＜ 1.14.1

References

URL	Tags
https://lists.apache.org/thread/qrvhmytsshsk5xcb68pwccw3y6m8o8nr	WEB

URL

Timeline

Published	2022-08-31	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.

Published

2022-08-31

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: org.apache.geode:geode-core

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven matched Mitigation candidate Open-source Maven artifact indexed by OSV (Maven packages: org.apache.geode:geode-core). The source is public, which makes an ARMR patch rule a candidate; nothing here establishes that one can be written.

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match decided it matched Protected by Waratek CWE-502 (Deserialization of Untrusted Data) is mitigable by an ARMR deserialization security rule.

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold skipped Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published skipped Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

apache geode not tracked cpe:2.3:a:apache:geode:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗