CVE-2014-5435
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 · uneditedAn arbitrary memory write vulnerability exists in the dual_onsrv.exe module in Honeywell Experion PKS R40x before R400.6, R41x before R410.6, and R43x before R430.2, that could lead to possible remote code execution or denial of service. Honeywell strongly encourages and recommends all customers running unsupported versions of EKPS prior to R400 to upgrade to a supported version.
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 confidenceArbitrary memory write vulnerability in the dual_onsrv.exe service module of Honeywell Experion PKS control systems. The flaw allows unauthenticated remote attackers to write to arbitrary memory locations, enabling potential remote code execution or denial of service against the control system network.
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>= r400, < r400.6>= r410, < r410.6>= r430, < r430.2CVSS 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.
-
Confirm Honeywell Experion PKS installationCheck system inventory or installed programs for Honeywell Experion Process Knowledge System. On Windows systems running Experion, check Program Files for Honeywell\Experion directory structure.Affected if Honeywell Experion PKS is not installed on the system
-
Identify Experion PKS versionCheck the installed Experion version. This is typically available through the Honeywell software installation, often visible in the About section of the Experion console, or via registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Honeywell\Experion if the server is Windows-based.Affected if Version cannot be determined or is not visible in standard locations
-
Compare version against affected rangesCompare the installed version to the affected ranges: r400.x (where x < 6), r410.x (where x < 6), or r430.x (where x < 2). Note that versions r400.6+, r410.6+, and r430.2+ are not affected.Affected if Installed version falls within >= r400 and < r400.6, OR >= r410 and < r410.6, OR >= r430 and < r430.2
-
Locate dual_onsrv.exe service moduleSearch for dual_onsrv.exe in the Experion installation directories, typically under the Experion server installation path (for example, in the Bin or Server folder within the Honeywell\Experion directory structure).Affected if dual_onsrv.exe is found and running as a service on the Experion system
-
Verify service statusCheck if the dual_onsrv.exe process is running. On Windows, use Task Manager or the command 'tasklist /FI "IMAGENAME eq dual_onsrv.exe"' to confirm the service is active.Affected if dual_onsrv.exe service is actively running on the control system
The system is affected if Honeywell Experion PKS is installed with a version that falls within the affected ranges (r400.x before r400.6, r410.x before r410.6, or r430.x before r430.2) AND the dual_onsrv.exe service module is present and running.
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.
dbcve · scopedUpgrade Honeywell Experion PKS to version R400.6 or later (R40x), R410.6 or later (R41x), or R430.2 or later (R43x). This is a critical infrastructure system requiring coordinated downtime and validation testing.
R400.6 (for r40x branch), R410.6 (for r41x branch), or R430.2 (for r43x branch)
- Identify the current Experion PKS version by checking the system information or consulting Honeywell documentation
- Determine which version branch (r40x, r41x, or r43x) is currently running
- Plan the upgrade path based on the current branch: if on r40x, upgrade to r400.6 or later; if on r41x, upgrade to r410.6 or later; if on r43x, upgrade to r430.2 or later
- Create a complete system backup before initiating any upgrade
- Review Honeywell's official upgrade documentation for Experion PKS
- Execute the upgrade following Honeywell's recommended procedures
- Verify the installation and test that all critical functions operate normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5435 — 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-2014-5435 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