dbcve.org
RangerApplication · Apache

CVE-2017-7676

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-14
Fix available
A fix is available. Upgrade to after 0.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Policy resource matcher in Apache Ranger before 0.7.1 ignores characters after '*' wildcard character - like my*test, test*.txt. This can result in unintended behavior.

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 · high confidence

Apache Ranger's policy resource matcher incorrectly handles the '*' wildcard character in resource path patterns. When a pattern like 'test*.txt' is used, any characters appearing after the '*' are ignored by the matcher, causing the pattern to match any resource starting with 'test' rather than only files matching 'test*.txt'. This allows attackers to access resources outside the intended policy scope.

MitigationUpgrade Apache Ranger to version 0.7.1 or later where the wildcard matching behavior is corrected. Review existing policies using '*' wildcards to ensure they enforce the intended access controls.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Apache Ranger version
    Identify the installed version of Apache Ranger by reviewing the Ranger admin interface version display, or checking the ranger-admin or ranger-usersync WAR file version, or running 'rpm -q ranger-admin' or 'dpkg -l | grep ranger' depending on your package manager.
    Affected if The installed version is 0.7.0 or earlier.
  2. Identify policies with wildcard patterns
    In the Ranger admin console, navigate to the Policies section and review each resource service policy. Look for any resource path definitions that contain the '*' character, such as 'path/to/file*.txt' or '/data/*.json'.
    Affected if Any policy contains resource paths with '*' wildcards in path patterns.
  3. Verify wildcard pattern matching behavior
    Create a test policy using a pattern with '*' followed by additional characters (for example, 'test*.txt') and attempt to access a resource that matches only the prefix before '*' (for example, 'testfile' without '.txt'). If access is granted when it should not be, the vulnerability is present.
    Affected if A pattern like 'test*.txt' incorrectly grants access to 'testfile' (files missing the '.txt' suffix).

You are affected if Apache Ranger version is 0.7.0 or earlier AND you have policies using '*' wildcard characters in resource path patterns.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.7.0
Interim mitigation

Upgrade Apache Ranger to version 0.7.1 or later where the wildcard matching behavior is corrected. Review existing policies using '*' wildcards to ensure they enforce the intended access controls.

Recommended fix High confidence

Apache Ranger 0.7.1

  1. 1. Review current Apache Ranger version by checking the installed version or release notes
  2. 2. Download Apache Ranger 0.7.1 or later from the official Apache repository (archive.apache.org)
  3. 3. Follow the standard Apache Ranger upgrade procedure documented in the Ranger upgrade guide
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Verify that the policy resource matcher correctly handles wildcard patterns like my*test and test*.txt after the upgrade
  6. 6. Deploy the upgraded version to production
Caveat Review Ranger 0.7.1 release notes for any breaking changes between your current version and 0.7.1; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-7676 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