CVE-2018-11064
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 · uneditedDell EMC Unity OE versions 4.3.0.x and 4.3.1.x and UnityVSA OE versions 4.3.0.x and 4.3.1.x contains an Incorrect File Permissions vulnerability. A locally authenticated malicious user could potentially exploit this vulnerability to alter multiple library files in service tools that might result in arbitrary code execution with elevated privileges. No user file systems are directly affected by this vulnerability.
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 confidenceThis vulnerability in Dell EMC Unity and UnityVSA allows a locally authenticated user to modify library files in service tools due to incorrect file permissions. Successful exploitation enables arbitrary code execution with elevated (root/administrator) privileges. The attack requires local authentication and targets system service tool libraries, not user file systems.
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>= 4.3.0.1522077968, <= 4.3.1.1525703027>= 4.3.0.1522077968, <= 4.3.1.1525703027CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Unity OE versionRun 'version' or 'show version' command in the Unity service console, or check via Unisphere GUI under Settings > AboutAffected if The displayed version falls between 4.3.0.1522077968 and 4.3.1.1525703027 inclusive
-
Confirm product is Unity or UnityVSAVerify the installed product is Dell EMC Unity (hardware) or UnityVSA (virtual) using 'version' output or Unisphere interfaceAffected if Product is Unity or UnityVSA with version in the affected range
-
Locate service tool library filesBrowse to service tool directories (typically under /service or similar paths containing tool binaries and shared libraries)Affected if Service tool directories exist and contain library files (*.so, *.dll, *.dylib) that are world-writable or group-writable
-
Check file permissions on service librariesUse 'ls -la' or 'icacls' command on identified service tool library files to inspect permissionsAffected if Any service tool library files show write permissions for unprivileged users (world-writable or writable by non-admin groups)
-
Verify write access for low-privilege usersAttempt to create or modify a test file in service tool directories using a non-privileged local accountAffected if Write access is granted to non-service, non-admin users in service tool library directories
If the Unity OE version is between 4.3.0.1522077968 and 4.3.1.1525703027 AND service tool library files are writable by non-privileged users, the environment is vulnerable.
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 dataApply the vendor-supplied Unity OE patch or update to a non-vulnerable version (beyond 4.3.1.x), and review file permissions on service tool libraries to ensure only privileged service accounts have write access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11064 — 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-2018-11064 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