GeodeApplication · Apache
CVE-2017-9795
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 cluster before v1.3.0 is operating in secure mode, a user with read access to specific regions within a Geode cluster may execute OQL queries that allow read and write access to objects within unauthorized regions. In addition a user could invoke methods that allow remote code execution.
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 before v1.3.0 has an authorization bypass in secure mode where users with read access to specific regions can execute OQL queries that bypass authorization checks, enabling read/write access to unauthorized regions and invocation of methods leading to remote code execution.
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.3.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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.
-
Determine installed Apache Geode versionRun 'gfsh version' or check the geode-core JAR manifest file in the installation directory, or query the cluster using 'describe version' command if connected to a locatorAffected if The version number is lower than 1.3.0 (for example 1.2.0, 1.1.0, 1.0.x, etc.)
-
Verify if security is enabledInspect the geode.properties or gemfire.properties configuration file for the 'security-enabled' property, or run 'gfsh show configuration' and check if security-manager is configuredAffected if security-enabled is set to true or a security-manager is defined in the configuration
-
Check if OQL query service is accessibleVerify that the Geode cluster allows OQL query execution via gfsh 'query' command or through client applications connected to the clusterAffected if OQL queries can be executed against the cluster, indicating the query service is enabled and accessible
-
Identify region access configurationReview the security.xml or security policy configuration files that define which users have read access to specific regions, and check for any overly permissive region access grantsAffected if Users exist with read-only access to certain regions, as the vulnerability allows these users to bypass and access other regions they should not have access to
You are affected if you are running Apache Geode version 1.3.0 or earlier with security enabled and OQL query service accessible, where users with limited region access could potentially bypass authorization through OQL queries.
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 data1.3.0
Upgrade to Apache Geode v1.3.0 or later to patch the authorization bypass vulnerability in OQL query processing.
Fix this in Geode
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9795 — 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-9795 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