GHSA-jmg4-x4vp-6c6x CVE-2017-15695
Apache Geode vulnerable to Incorrect Authorization
High
Maven
- Severity
- 8.8 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 2.51%
- Chance of exploitation in the next 30 days. Higher than 84.79% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-863 Incorrect Authorization
- Fix
1.5.0- Upgrade org.apache.geode:geode-core to this version or later
Description
When an Apache Geode server versions 1.0.0 to 1.4.0 is configured with a security manager, a user with DATA:WRITE privileges is allowed to deploy code by invoking an internal Geode function. This allows remote code execution. Code deployment should be restricted to users with DATA:MANAGE privilege.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.geode:geode-core | >= 1.0.0, < 1.5.0 |
1.5.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.5.0
- maven
<dependency><groupId>org.apache.geode</groupId><artifactId>geode-core</artifactId><version>1.5.0</version></dependency>- gradle
implementation("org.apache.geode:geode-core:1.5.0")
Severity breakdown
CVSS 3.0 8.8
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-863: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
- github.com/apache/geode/pull/1258
- github.com/apache/geode/commit/00be4f9774e1adf8e7ccc2664da8005fc30bb11d
- github.com/apache/geode/commit/49d28f93fd2ef069693ce15d124ef3a29f22fb7d
- github.com/apache/geode/commit/6df14c8b1e3c644f9f810149e80bba0c2f073dab
- github.com/apache/geode/commit/740289c61d60256c6270756bc84b9e24b76e4913
- github.com/apache/geode/commit/90f8f6242927c5e16da64f38bba9abf3d450a305
- github.com/apache/geode/commit/954ccb545d24a9c9a35cbd84023a4d7e07032de0
- github.com/apache/geode/commit/aa469239860778eb46e09dd7b390aee08f152480
- cwiki.apache.org/confluence/display/GEODE/Release+Notes
- issues.apache.org/jira/browse/GEODE-3974
- lists.apache.org/thread.html/dc8875c0b924885a884eba6d5bd7dc3f123411b2d33cffd00e351c99…
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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