CVE-2018-14804
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 AMS Device Manager v12.0 to v13.5. A specially crafted script may be run that allows arbitrary remote 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 confidenceEmerson AMS Device Manager versions 12.0 through 13.5 contains a vulnerability that allows execution of specially crafted scripts, leading to arbitrary remote code execution (RCE) with critical severity (CVSS 9.8).
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>= 12.0, <= 13.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Locate Emerson AMS Device Manager installationCheck for the AMS Device Manager application in typical installation directories such as C:\Program Files\Emerson\AMS Device Manager or C:\Program Files (x86)\Emerson\AMS Device Manager on Windows systems. Also verify if the service 'AMS Device Manager' exists in Windows Services.Affected if The application is found installed on the system
-
Determine installed versionOpen the application or check the executable properties. Right-click on AMSDeviceManager.exe or similar executable, select Properties, and view the Version tab. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Emerson\AMS Device Manager for the Version value.Affected if The installed version falls within the range 12.0 to 13.5 inclusive
-
Verify script execution component is presentCheck for the presence of script execution functionality within AMS Device Manager. Look for directories or modules related to scripting such as Scripting, Automation, or similar features within the application installation folder.Affected if The script execution module or feature is installed and accessible within the application
-
Assess network exposure of management interfaceCheck if AMS Device Manager management interface is bound to accessible network interfaces. Review the application configuration for listening addresses and verify network accessibility using netstat -an | findstr for typical AMS ports.Affected if The management interface is bound to a reachable network address rather than localhost only
You are affected if Emerson AMS Device Manager version 12.0 through 13.5 is installed with the script execution feature 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 dataUpgrade to a patched version of Emerson AMS Device Manager. If immediate patching is not feasible, restrict network access to the AMS Device Manager interface and implement strict input validation on any script execution paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14804 — 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-14804 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