GeodeApplication · Apache
CVE-2022-37023
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.
NVD · uneditedApache Geode versions prior to 1.15.0 are vulnerable to a deserialization of untrusted data flaw when using REST API on Java 8 or Java 11. Any user wishing to protect against deserialization attacks involving REST APIs should upgrade to Apache Geode 1.15 and follow the documentation for details on enabling "validate-serializable-objects=true" and specifying any user classes that may be serialized/deserialized with "serializable-object-filter". Enabling "validate-serializable-objects" may impact performance.
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.
dbcve analysis · high confidenceApache Geode versions prior to 1.15.0 contain a deserialization vulnerability in the REST API when running on Java 8 or Java 11, allowing deserialization of untrusted data through REST endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data
GeodeApplication
< 1.15.0CVSS 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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Apache Geode versionRun 'gfsh version' or check the geode-core jar file version in the installation directoryAffected if Version is below 1.15.0 (e.g., 1.14.x, 1.13.x, etc.)
-
Check Java runtime versionRun 'java -version' and examine the outputAffected if Java 8 or Java 11 is in use (the vulnerability does not affect Java 17+)
-
Verify REST API is enabledCheck Geode configuration files (geode.properties or cache.xml) for 'http-service' or 'rest-api' enabled settings, or check if port 8080 is listeningAffected if REST API service is listening and accessible on the configured port
-
Confirm network exposure of REST endpointsInspect firewall rules and bind address configuration to determine if REST endpoints are reachable from networkAffected if REST API is exposed to untrusted networks rather than localhost-only
Affected if Apache Geode version is below 1.15.0 AND Java 8 or 11 is in use AND the REST API is enabled and accessible
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped1.15.0
Upgrade to Apache Geode 1.15.0 or later and enable 'validate-serializable-objects=true' with appropriate 'serializable-object-filter' configuration to restrict allowed serializable classes.
Apache Geode 1.15.0
- Upgrade to Apache Geode 1.15.0
- Review the official Apache Geode documentation on securing deserialization
- Enable 'validate-serializable-objects=true' in your Geode configuration
- Configure 'serializable-object-filter' to specify trusted classes that may be serialized/deserialized
- Test the configuration in a non-production environment before deploying
- Monitor for performance impact after enabling validation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Geode
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-37023 in production — separate from our analysis above.
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.
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.
- 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