Apache Geode OQL bind parameter vulnerability

published 2018-01-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-q7cp-r6cj-hpf5 , EUVD-2022-4909

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

When 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 containing a region name as a bind parameter that allow read access to objects within unauthorized regions.

Patch / fix

fixed in 2

maven org.apache.geode:geode-core 1.3.0
apache geode 1.3.0

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:P/I:N/A:N
GitHub	3.0	5.3	CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.apache.geode:geode-core	>=1.0.0, <1.3.0	1.3.0

Affected products

Apache Software Foundation Apache Geode

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

CVE List CVE-2017-9796
GitHub Advisory GHSA-q7cp-r6cj-hpf5
NVD CVE-2017-9796

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary