GeodeApplication · Apache

CVE-2022-37022

HIGH · 8.8 CVSS v3.1 Published 2022-08-31

Fix available

A fix is available. Upgrade to after 1.13.2 or later.

See remediation →

94/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

NVD · unedited

Apache Geode versions up to 1.12.2 and 1.13.2 are vulnerable to a deserialization of untrusted data flaw when using JMX over RMI on Java 11. Any user wishing to protect against deserialization attacks involving JMX or RMI should upgrade to Apache Geode 1.15. Use of 1.15 on Java 11 will automatically protect JMX over RMI against deserialization attacks. This should have no impact on performance since it only affects JMX/RMI which Gfsh uses to communicate with the JMX Manager which is hosted on a Locator.

Technical summary

dbcve analysis · high confidence

Apache Geode versions up to 1.12.2 and 1.13.2 contain a deserialization of untrusted data vulnerability when using JMX over RMI on Java 11, which could allow remote code execution via malicious serialized objects.

MitigationUpgrade to Apache Geode 1.15 or later, which automatically protects JMX over RMI against deserialization attacks when running on Java 11.

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

Affected products & versions

NVD · CPE data

GeodeApplication

Affected:<= 1.12.2>= 1.13.0, <= 1.13.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Identify installed Apache Geode version

Run 'gfsh version' or check the geode-core JAR manifest, or inspect the geode installation directory for version information

Affected if Version is 1.12.2 or lower, or between 1.13.0 and 1.13.2 inclusive
Verify Java version in use

Run 'java -version' to confirm Java 11 is the runtime environment

Affected if Java 11 is the active JDK/JRE version
Confirm JMX over RMI is enabled

Check configuration files (gemfire.properties, gfsh properties) for JMX manager configuration with RMI connector. Also check for environment variables like JMX_REMOTE_PORT or javax.management.remote.rmi.port that indicate RMI-based JMX is active

Affected if JMX over RMI connector is configured and active

Environment is affected only if all three conditions are true: Apache Geode version is within 1.12.2 or lower, or 1.13.0-1.13.2, Java 11 is running, AND JMX over RMI is explicitly enabled/configured

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 1.13.2

Interim mitigation

Upgrade to Apache Geode 1.15 or later, which automatically protects JMX over RMI against deserialization attacks when running on Java 11.

Recommended fix High confidence

Apache Geode 1.15

Stop all running Geode processes (locators, servers, and any Gfsh connections)
Download Apache Geode 1.15 from the official Apache Geode distribution (https://geode.apache.org/releases/)
Install Apache Geode 1.15 on all nodes in the cluster, replacing the previous installation
Update any scripts, automation, or documentation that reference the old Geode version or installation paths
Restart the Locator first to establish the JMX Manager
Restart any servers and reconnect using Gfsh to verify the cluster is operational
If running on Java 11, verify that JMX over RMI connections are now protected against deserialization attacks

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

Fix this in Geode Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

11.0 hours of engineering $1,900

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-37022 — 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

Primary sources

lists.apache.orgMailing ListVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-37022?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 1.13.2 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 1.3%

Affects: Geode

Remediation

A high-priority fix

Fix this in Geode 11 hrs · Moderate

Typical engagement from $1,900

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-37022 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References