OozieApplication · Apache
CVE-2017-15712
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 · uneditedVulnerability allows a user of Apache Oozie 3.1.3-incubating to 4.3.0 and 5.0.0-beta1 to expose private files on the Oozie server process. The malicious user can construct a workflow XML file containing XML directives and configuration that reference sensitive files on the Oozie server host.
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 Oozie allows users to submit workflow XML files containing XML directives that can reference sensitive files on the Oozie server host, enabling unauthorized file read access. This is likely an XML External Entity (XXE) injection or path traversal vulnerability in the workflow XML parsing process.
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
OozieApplication
= 3.1.2= 3.1.3= 3.2= 3.2.0= 3.3.0= 3.3.1= 3.3.2= 4.0.0= 4.0.1= 4.1.0= 4.2.0= 4.3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Oozie versionRun 'oozie version' or check the Oozie web UI (/oozie/admin/version) to retrieve the exact version numberAffected if The version matches any of these: 3.1.2, 3.1.3, 3.2, 3.2.0, 3.3.0, 3.3.1, 3.3.2, 4.0.0, 4.1.0, 4.2.0, 4.3.0
-
Verify Oozie service is runningCheck if the Oozie server process is active and the web UI is accessible on the configured port (typically 11000)Affected if The service is running and accepts workflow job submissions
-
Confirm workflow XML submission is enabledReview Oozie configuration (oozie-site.xml) for the 'oozie.service.WorkflowJobXCommand' or similar submission-related service settings that allow users to submit XML workflowsAffected if Workflow XML submission is permitted for users or unauthenticated callers
-
Inspect XML parser configuration for external entity handlingCheck Oozie configuration files for XML parser settings. Look for properties like 'javax.xml.parsers.DocumentBuilderFactory' or similar XXE-related configurations that may enable or disable external entity processingAffected if XML external entities are not explicitly disabled in the parser configuration
You are affected if Oozie is running a version between 3.1.2 and 4.3.0 inclusive AND allows workflow XML submissions with XML parsers that permit external entity processing.
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 Oozie to a patched version (4.3.1+ or 5.0+) and disable XML external entity processing in the XML parser configuration. Alternatively, implement strict file system permissions and input validation for workflow XML submissions.
Fix this in Oozie
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15712 — 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-2017-15712 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