GeodeApplication · Apache
CVE-2017-15694
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 · uneditedWhen an Apache Geode server versions 1.0.0 to 1.8.0 is operating in secure mode, a user with write permissions for specific data regions can modify internal cluster metadata. A malicious user could modify this data in a way that affects the operation of the cluster.
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 · moderate confidenceIn Apache Geode versions 1.0.0 to 1.8.0, the authorization model fails to properly separate user data regions from internal cluster metadata. When running in secure mode, users granted write permissions to specific data regions can also modify internal cluster metadata, allowing manipulation of cluster operation.
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.0.0, <= 1.8.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
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 versionCheck the installed Geode version by running 'geode --version' or inspecting the installed geode-core JAR file name and version metadata.Affected if The installed version is between 1.0.0 and 1.8.0 inclusive.
-
Confirm secure mode is enabledInspect the Geode cluster configuration or the gfsecurity properties file for security-enabled settings. Look for 'security-client-auth-init' or 'security-manager' configuration properties in the cluster's properties file or distributed system configuration.Affected if The cluster is running with security enabled (secure mode is on).
-
Review data region write permissionsCheck the configured authorization permissions for data regions. This can be done by reviewing the security implementation (SecurityManager) or the authorization configuration that defines which users have write access to data regions.Affected if Users exist who have write permissions to one or more data regions in the cluster.
-
Verify metadata region isolationInspect the authorization configuration to confirm whether access controls explicitly separate data regions (like /trade, /account) from internal metadata regions (like /__clusterMetaData, /__indexMetaData or similar internal regions).Affected if The authorization configuration does not explicitly deny write access to internal cluster metadata regions for users who only need data region write access.
A user is affected if they run Apache Geode version 1.0.0 through 1.8.0 in secure mode with users having data region write permissions that are not explicitly restricted from modifying internal cluster metadata.
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.
From vendor dataUpgrade to Apache Geode version 1.9.0 or later, which contains the fix for this authorization bypass. Additionally, review user permissions to ensure proper separation between data region access and metadata manipulation.
Fix this in Geode
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15694 — 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-2017-15694 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