Skip to content

GHSA-wc4x-4gm2-74j8 CVE-2019-10091

Apache Geode SSL endpoint verification vulnerability

High Maven
Severity
7.4 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.42%
Chance of exploitation in the next 30 days. Higher than 72.79% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-295 Improper Certificate Validation
Fix
1.10.0
Upgrade org.apache.geode:geode-core to this version or later

Description

When TLS is enabled with ssl-endpoint-identification-enabled set to true, Apache Geode fails to perform hostname verification of the entries in the certificate SAN during the SSL handshake. This could compromise intra-cluster communication using a man-in-the-middle attack.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.geode:geode-core
< 1.10.0
1.10.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.10.0

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

Severity breakdown

CVSS 3.1 7.4

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

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

Weakness

CWE-295: Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

How to prevent it
  • Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

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