CVE-2018-14793
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 · uneditedDeltaV Versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, and R5 is vulnerable to a buffer overflow exploit through an open communication port to 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 · moderate confidenceA buffer overflow vulnerability exists in DeltaV distributed control system versions 11.3.1, 12.3.1, 13.3.0, 13.3.1, and R5. The flaw is exploitable through an open communication port, allowing an attacker to overflow a memory buffer and execute arbitrary code with the privileges of the affected 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= 11.3.1= 12.3.1= 13.3.0= 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/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 software is installedCheck system programs, installed software list, or look for DeltaV processes running on the system using task manager or system inventory toolsAffected if DeltaV distributed control system software is present on the machine
-
Determine the installed DeltaV versionAccess DeltaV system information through the control system interface, check the About or Version section in the DeltaV software, or query the system using Emerson-provided diagnostic toolsAffected if The installed version is exactly 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5
-
Locate the exposed communication portReview network configuration documentation or use netstat -an to identify listening ports on the DeltaV system. Consult Emerson documentation for DeltaV network services and default portsAffected if A network service port associated with DeltaV is open and listening for external connections
-
Verify network accessibility of the DeltaV portUse network scanning tools (such as nmap) from an external system to determine if the DeltaV communication port is accessible from the network, or check firewall rules for permitted inbound connectionsAffected if The DeltaV communication port is reachable from network segments that are not isolated by firewalls or network segmentation
You are affected if DeltaV version 11.3.1, 12.3.1, 13.3.0, 13.3.1, or R5 is running AND the vulnerable communication port is network-accessible
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 network segmentation and firewall controls to restrict access to the vulnerable communication port. Coordinate with Emerson for available patches and consider compensating controls such as disabling unnecessary network services until remediation can be completed.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14793 — 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-14793 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