DeltavApplication · Emerson

CVE-2018-14797

HIGH · 7.8 CVSS v3.1 Published 2018-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Emerson DeltaV DCS versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, R5 allow a specially crafted DLL file to be placed in the search path and loaded as an internal and valid DLL, which may allow arbitrary code execution.

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

This is a DLL search order hijacking vulnerability in Emerson DeltaV DCS. An attacker can place a malicious DLL file in a directory that is part of the application's search path, causing the DCS software to load the crafted DLL instead of the legitimate one, leading to arbitrary code execution with the privileges of the DeltaV process.

MitigationOrganizations should apply vendor-supplied patches for DeltaV versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, and R5. Until patches are available, restrict file system permissions to prevent unauthorized users from placing files in application search paths and monitor for suspicious DLL files in DeltaV directories.

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
DeltavApplication
Affected:= 11.3.1= 12.3.1= 13.3.0= 13.3.1= r5

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify installed DeltaV version
    Check the DeltaV installation directory or use system inventory tools to find the installed version. Look in typical installation paths like C:\Program Files\Emerson\DeltaV or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Emerson\DeltaV
    Affected if The installed version matches 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5 exactly
  2. Enumerate DeltaV application directories
    Locate all directories containing DeltaV executables and application files. Check installation folders and search paths used by DeltaV applications
    Affected if DeltaV is installed and the application uses directories in its search path
  3. Inspect directories for unauthorized DLL files
    List all DLL files in DeltaV installation directories and subdirectories. Look for suspicious or unexpected DLL files that are not part of the standard DeltaV installation, especially in the application root or bin directories
    Affected if Unexpected or unknown DLL files exist in DeltaV directories, particularly in locations that would be searched before the Windows system directories
  4. Check file system permissions on DeltaV directories
    Review NTFS permissions on DeltaV installation directories and application folders. Use tools like icacls or examine share permissions to determine which users or groups can write to these locations
    Affected if Users other than administrators or authorized DeltaV service accounts have write permissions to DeltaV application directories

A user is affected if their installed DeltaV version is 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5 and unauthorized DLL files exist in DeltaV directories or non-privileged users have write access to application search paths.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should apply vendor-supplied patches for DeltaV versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, and R5. Until patches are available, restrict file system permissions to prevent unauthorized users from placing files in application search paths and monitor for suspicious DLL files in DeltaV directories.

Fix this in Deltav Scoped from the published advisory
  • Consultation12.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14797 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14797 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