RangerApplication · Apache

CVE-2017-7677

MEDIUM · 5.9 CVSS v3.0 Published 2017-06-14
Fix available
A fix is available. Upgrade to after 0.7.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Hive Authorizer in Apache Ranger versions before 0.7.1 fails to validate RWX (Read-Write-Execute) permissions when users create external Hive tables. External tables store data in user-specified locations outside the Hive warehouse, and the missing permission check could allow unauthorized table creation in arbitrary filesystem locations.

MitigationUpgrade Apache Ranger to version 0.7.1 or later, which implements proper RWX permission validation for external Hive table creation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RangerApplication
Affected:<= 0.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Ranger version
    Check the Ranger admin UI under 'Settings > System Info' or inspect the ranger-admin pom.xml file in the installation directory, or run 'ranger-admin version' if CLI is available
    Affected if version is 0.7.0 or earlier (any version <= 0.7.0)
  2. Confirm Hive Authorizer is enabled
    In Ranger admin UI, navigate to 'Access Manager > Resource Based Policies' and verify a Hive service policy exists and is enabled, or check the Hive plugin configuration file (ranger-hive-audit.xml or equivalent) for an active connection to Ranger
    Affected if Hive Authorizer plugin is connected to a Ranger policy server running the vulnerable version
  3. Verify external Hive table creation is permitted
    Check Ranger Hive policies for any resource policy that allows CREATE TABLE operations on external table paths (often denoted by database/table wildcards or specific external storage locations), or query existing external tables via 'SHOW CREATE TABLE' in Hive to confirm external location parameters are in use
    Affected if CREATE TABLE permissions exist for external tables (tables with LOCATION pointing outside the Hive warehouse)
  4. Inspect audit logs for unauthorized external table creation
    Review Ranger audit logs (typically in /var/log/ranger/audit/ or via the Ranger audit UI) for CREATE TABLE events where the table type is EXTERNAL and the location path is user-controlled outside the warehouse directory
    Affected if Audit logs show external tables were created in locations not explicitly authorized or outside expected paths

If Apache Ranger version 0.7.0 or earlier is deployed with the Hive Authorizer enabled and external Hive table creation is permitted via Ranger policies, the environment is vulnerable to CVE-2017-7677.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.7.0
Interim mitigation

Upgrade Apache Ranger to version 0.7.1 or later, which implements proper RWX permission validation for external Hive table creation.

Fix this in Ranger Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7677 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7677 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data