GHSA-7ccv-hhvc-62hg CVE-2015-0266
Apache Ranger allows users to bypass intended access restrictions via direct access to module URLs
High
Maven
- Severity
- 7.1 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 2.10%
- Chance of exploitation in the next 30 days. Higher than 81.73% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
0.5.0- Upgrade org.apache.ranger:ranger to this version or later
Description
The Policy Admin Tool in Apache Ranger before 0.5.0 allows remote authenticated users to bypass intended access restrictions via direct access to module URLs.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.ranger:ranger | < 0.5.0 |
0.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.ranger:ranger Maven → 0.5.0
- maven
<dependency><groupId>org.apache.ranger</groupId><artifactId>ranger</artifactId><version>0.5.0</version></dependency>- gradle
implementation("org.apache.ranger:ranger:0.5.0")
Severity breakdown
CVSS 3.0 7.1
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
Weakness
CWE-639: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How to prevent it
- Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
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
- cwiki.apache.org/confluence/display/RANGER/Vulnerabilities+found+in+Ranger
- mail-archives.apache.org/mod_mbox/ranger-dev/201508.mbox/%3CD1E7EC30.9D53F%25vel%40apache.org%3E
- mail-archives.apache.org/mod_mbox/ranger-dev/201508.mbox/%3CD1E7EC30.9D53F%25vel@apache.org%3E
- web.archive.org/web/20200228073944/http://www.securityfocus.com/bid/76221
- slideshare.net/wojdwo/big-problems-with-big-data-hadoop-interfaces-security
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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-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 |
| GHSA-fpqp-v323-44xv Cross-site scripting in Apache Ranger | Medium | Also affects org.apache.ranger:ranger |
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