CVE-2017-9797 json
Apache Geode vulnerable to Exposure of Sensitive Information
published 2017-10-02 9 y ago modified 2026-06-17 4 mo ago also GHSA-vh98-fqfc-4hj3 , EUVD-2022-5357
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
When an Apache Geode cluster before v1.2.1 is operating in secure mode, an unauthenticated client can enter multi-user authentication mode and send metadata messages. These metadata operations could leak information about application data types. In addition, an attacker could perform a denial of service attack on the cluster.
Patch / fix
- maven org.apache.geode:geode-core 1.2.1
Exploit prediction
1.36% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:N/A:P |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.geode:geode-core | >=1.0.0, <1.2.1 |
1.2.1 |
Affected products
- Apache Software Foundation Apache Geode
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
mail-archives.apache.org
/mod_mbox/geode-user/201709.mbox/%3cCAEwge-Hrbb7JS8Nygrh7geyFvW4bMZ3AdCmPOzMfvbniipz0bA%40mail.gmail.com%3e
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2017-9797
advisory
-
cwiki.apache.org
/confluence/display/GEODE/Release+Notes#ReleaseNotes-SecurityVulnerabilities
web
-
issues.apache.org
/jira/browse/GEODE-3249
web
-
mail-archives.apache.org
/mod_mbox/geode-user/201709.mbox/%3cCAEwge-Hrbb7JS8Nygrh7geyFvW4bMZ3AdCmPOzMfvbniipz0bA@mail.gmail.com%3e
web
Sources
- CVE List CVE-2017-9797
- GitHub Advisory GHSA-vh98-fqfc-4hj3
- NVD CVE-2017-9797
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.