GeodeApplication · Apache
CVE-2022-34870
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 up to 1.15.0 are vulnerable to a Cross-Site Scripting (XSS) via data injection when using Pulse web application to view Region entries.
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 Pulse web application fails to properly sanitize user-controlled data when displaying Region entries, allowing authenticated attackers to inject malicious JavaScript that executes in the context of other users' browsers.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify Apache Geode installation and versionRun 'gfsh version' or check the installed Geode JAR files for the version number, or query the management API for the product versionAffected if The installed version is 1.15.0 or lower
-
Verify Pulse web application is enabledCheck Geode configuration files (gemfire.properties or geode.properties) for 'pulse' settings, or check if the Pulse WAR is deployed in the apps directoryAffected if Pulse web application is deployed and accessible
-
Confirm Region data is viewable through PulseAccess the Pulse web UI and navigate to the Region viewer functionality to see if data entries are displayedAffected if Regions exist and can be viewed through the Pulse interface
-
Inspect browser for XSS executionIn a controlled test environment, add a benign script tag as Region data (e.g., <script>alert('XSS')</script>) and view it through Pulse; check if the script executes in the browserAffected if The script tag is rendered literally in the browser without encoding or sanitization
You are affected if Apache Geode version 1.15.0 or lower is running with the Pulse web application enabled and regions containing untrusted data are viewable through the Pulse interface.
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 · scopedUpgrade to Apache Geode version 1.15.0 or later, or implement output encoding and input validation on data displayed in the Pulse web application Region entry viewer.
Upgrade to Apache Geode 1.15.1 or later (such as 1.16.0)
- 1. Identify the current Apache Geode version in use by checking the installed Geode distribution or gfsh version command
- 2. Download Apache Geode version 1.15.1 or later from the official Apache Geode downloads page (https://geode.apache.org/releases/)
- 3. Before upgrading, back up all critical data, configuration files (gemfire.properties, gfsecurity.properties), and any persisted region data
- 4. Stop all running Geode servers, locators, and applications connected to the cluster
- 5. Install the new Geode version on all nodes in the cluster
- 6. Update any PATH or environment variables to reference the new Geode installation
- 7. Restart the Geode cluster using the new version
- 8. Verify that the Pulse web application is accessible and functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Geode
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34870 — 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-34870 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