CVE-2018-14791
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 · uneditedEmerson DeltaV DCS versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, R5 may allow non-administrative users to change executable and library files on the affected products.
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 confidenceEmerson DeltaV DCS versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, and R5 contain an authorization vulnerability that allows non-administrative users to modify executable and library files on the affected system, potentially enabling code execution or system compromise.
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= 11.3.1= 12.3.1= 13.3= 13.3.1= r5CVSS 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.1/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 if DeltaV DCS is installedLocate DeltaV installation directories on the system, typically found in the program files or application directories. Check for DeltaV-specific folders or services.Affected if DeltaV DCS software is present on the system
-
Determine the installed DeltaV versionAccess the DeltaV system information or About section through the DeltaV Explorer or control system interface to view the exact version number.Affected if The installed version matches 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5
-
Verify file system permissions on executable directoriesExamine the file system permissions on DeltaV directories containing executable files (.exe, .dll) and library files. Check write access for non-administrative user accounts.Affected if Non-administrative users have write permissions to executable or library directories
-
Review user role assignments and RBAC configurationAccess the DeltaV user management or security configuration to list all user roles and their assigned permissions, particularly focusing on file modification privileges.Affected if Non-administrative user accounts are assigned roles that permit modification of executable or library files
A system is affected if DeltaV DCS versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5 are installed and non-administrative users have write access to executable or library file directories.
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 vendor-supplied patches for DeltaV DCS and review user role-based access control (RBAC) configurations to enforce least-privilege principles; restrict file system permissions on executable and library directories to administrative users only.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14791 — 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-14791 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