Skip to content

GHSA-ffjh-fjgg-mfpq CVE-2017-7677

Moderate severity vulnerability that affects org.apache.ranger:ranger

Medium Maven
Severity
5.9 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
2.61%
Chance of exploitation in the next 30 days. Higher than 85.43% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-862 Missing Authorization
Fix
0.7.1
Upgrade org.apache.ranger:ranger to this version or later

Description

In environments that use external location for hive tables, Hive Authorizer in Apache Ranger before 0.7.1 should be checking RWX permission for create table.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.ranger:ranger
< 0.7.1
0.7.1

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.ranger:ranger Maven → 0.7.1

maven
<dependency><groupId>org.apache.ranger</groupId><artifactId>ranger</artifactId><version>0.7.1</version></dependency>
gradle
implementation("org.apache.ranger:ranger:0.7.1")

Severity breakdown

CVSS 3.0 5.9

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

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

Weakness

CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-6qc3-v8fv-fv9j
Apache Ranger has a Command Injection vulnerability
Critical Also affects org.apache.ranger:ranger
GHSA-g9gf-g5jq-9h3v
Apache Ranger UI vulnerable to Server Side Request Forgery
Critical Also affects org.apache.ranger:ranger
GHSA-vrx2-mgr9-v67h
Apache Ranger has Stored Cross-site Scripting vulnerability in Edit Service Page
Medium Also affects org.apache.ranger:ranger
GHSA-89gw-cffj-mqg9
Apache Ranger code execution vulnerability in policy expressions
High Also affects org.apache.ranger:ranger
GHSA-83m2-9g78-rrj4
Apache Ranger Cross-site Scripting vulnerability
Medium Also affects org.apache.ranger:ranger
GHSA-7ccv-hhvc-62hg
Apache Ranger allows users to bypass intended access restrictions via direct access to module URLs
High Also affects org.apache.ranger:ranger
GHSA-qqg7-gcxw-gmj3
Apache Ranger allows users to bypass intended access restrictions via the REST API
Medium Also affects org.apache.ranger:ranger
GHSA-22v7-w6c5-v4rr
Apache Ranger Access Restriction Bypass
High Also affects org.apache.ranger:ranger
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