Skip to content

GHSA-g569-49wg-jx5f CVE-2017-15696

Apache Geode configuration request authorization vulnerability

High Maven
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.00%
Chance of exploitation in the next 30 days. Higher than 80.81% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.4.0
Upgrade org.apache.geode:geode-core to this version or later

Description

When an Apache Geode cluster before v1.4.0 is operating in secure mode, the Geode configuration service does not properly authorize configuration requests. This allows an unprivileged user who gains access to the Geode locator to extract configuration data and previously deployed application code.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.geode:geode-core
>= 1.0.0, < 1.4.0
1.4.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.geode:geode-core Maven → 1.4.0

maven
<dependency><groupId>org.apache.geode</groupId><artifactId>geode-core</artifactId><version>1.4.0</version></dependency>
gradle
implementation("org.apache.geode:geode-core:1.4.0")

Severity breakdown

CVSS 3.0 7.5

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-373r-9mg8-3jc4
Apache Geode vulnerable to Cross-Site Scripting
Medium Also affects org.apache.geode:geode-core
GHSA-qf8g-vpwp-6579
Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11
High Also affects org.apache.geode:geode-core
GHSA-q4q3-r45f-7gwg
Apache Geode vulnerable to Deserialization of Untrusted Data
Critical Also affects org.apache.geode:geode-core
GHSA-72x9-48mc-phh6
Apache Geode versions prior to 1.15.0 are vulnerable to a deserialization of untrusted data
Medium Also affects org.apache.geode:geode-core
GHSA-2gw6-73wc-x88f
Apache Geode information disclosure vulnerability
High Also affects org.apache.geode:geode-core
GHSA-37m3-qp37-x3c6
Apache Geode gfsh query vulnerability
Medium Also affects org.apache.geode:geode-core
GHSA-h22r-h77w-2g5f
Apache Geode gfsh authorization vulnerability
High Also affects org.apache.geode:geode-core
GHSA-q7cp-r6cj-hpf5
Apache Geode OQL bind parameter vulnerability
Medium Also affects org.apache.geode:geode-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor