RangerApplication · Apache
CVE-2019-12397
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 · uneditedPolicy import functionality in Apache Ranger 0.7.0 to 1.2.0 is vulnerable to a cross-site scripting issue. Upgrade to 2.0.0 or later version of Apache Ranger with the fix.
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 confidenceApache Ranger versions 0.7.0 through 1.2.0 contain a cross-site scripting (XSS) vulnerability in the policy import functionality. An attacker could inject malicious scripts through imported policy files that would be executed in the context of other users' sessions when viewing the policy admin interface.
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
>= 0.7.0, <= 1.2.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Ranger installation and versionCheck the installed Apache Ranger version. Common methods: (1) Review the Ranger admin UI footer which displays the version, (2) Check the ranger-admin or ranger version file in the installation directory, (3) Query the Ranger admin REST API endpoint /service/public/v3/api/versionAffected if The installed version falls within 0.7.0 through 1.2.0 inclusive
-
Verify Ranger admin web interface is accessibleConfirm that the Apache Ranger admin web interface (typically on port 6080) is reachable via browser or API. Attempt to access the login page at http://<ranger-host>:6080/Affected if The Ranger admin interface is accessible and responds, indicating an active installation
-
Confirm policy import feature is availableLog into the Ranger admin interface and navigate to the Policy Manager section. Locate the policy import/export functionality (usually under Settings > Policies or a dedicated Import/Export option)Affected if The policy import feature exists and is accessible to users with admin or policy management permissions
-
Check user access to policy viewingIdentify users who have access to view imported policies in the policy admin interface. These users would be able to trigger the XSS payload when viewing maliciously crafted policy filesAffected if Any user account with permission to view imported policies exists in the system
You are affected if Apache Ranger version 0.7.0-1.2.0 is installed AND the policy import feature is accessible to users who can view imported policies in the admin interface.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Apache Ranger to version 2.0.0 or later to obtain the fixed version. If immediate upgrade is not possible, restrict access to the policy import functionality to trusted administrators only.
Fix this in Ranger
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12397 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12397 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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