dbcve.org
Experion Lx FirmwareOperating system · Honeywell

CVE-2022-30317

CRITICAL · 9.1 CVSS v3.1 Published 2022-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Honeywell Experion LX through 2022-05-06 has Missing Authentication for a Critical Function. According to FSCT-2022-0055, there is a Honeywell Experion LX Control Data Access (CDA) EpicMo protocol with unauthenticated functionality issue. The affected components are characterized as: Honeywell Control Data Access (CDA) EpicMo (55565/TCP). The potential impact is: Firmware manipulation, Denial of service. The Honeywell Experion LX Distributed Control System (DCS) utilizes the Control Data Access (CDA) EpicMo protocol (55565/TCP) for device diagnostics and maintenance purposes. This protocol does not have any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality. There is no authentication functionality on the protocol in question. An attacker capable of invoking the protocols' functionalities could issue firmware download commands potentially allowing for firmware manipulation and reboot devices causing denial of service.

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

Honeywell Experion LX DCS uses the Control Data Access (CDA) EpicMo protocol on port 55565/TCP for device diagnostics and maintenance. This protocol lacks any authentication mechanism, enabling unauthenticated remote attackers to invoke critical functions including firmware download commands and device reboots, leading to firmware manipulation or denial of service.

MitigationImplement network segmentation and firewall rules to restrict access to port 55565/TCP to only authorized management stations; additionally, monitor for unauthorized CDA protocol communication patterns.

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
Experion Lx FirmwareOperating system
Affected:< r520.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm Honeywell Experion LX DCS presence
    Identify if Honeywell Experion LX DCS system is installed in the environment by reviewing asset inventory or system documentation
    Affected if System is identified as Honeywell Experion LX DCS
  2. Check installed firmware version
    Access the Control Data Access (CDA) system management interface or use vendor-provided diagnostic tools to determine the current firmware version; compare against r520.1 threshold
    Affected if Firmware version is below r520.1
  3. Verify CDA EpicMo protocol is enabled
    Check system configuration to confirm the Control Data Access (CDA) EpicMo protocol is enabled and running on the DCS system
    Affected if CDA EpicMo protocol is enabled and configured
  4. Confirm port 55565/TCP is exposed
    Perform a network scan or check firewall rules to determine if port 55565/TCP is open and reachable on the Experion LX system
    Affected if Port 55565/TCP is listening and accessible from network segments outside of authorized management stations

User is affected if running Honeywell Experion LX DCS with firmware below r520.1, where the unauthenticated CDA EpicMo protocol on port 55565/TCP is enabled and accessible from unauthorized network segments

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network segmentation and firewall rules to restrict access to port 55565/TCP to only authorized management stations; additionally, monitor for unauthorized CDA protocol communication patterns.

Recommended fix High confidence

Experion Lx Firmware r520.1 or later

  1. Backup the current Experion LX system configuration and firmware before proceeding with any changes
  2. Contact Honeywell official support to obtain the r520.1 or later firmware upgrade package
  3. Review Honeywell's official firmware upgrade documentation for Experion LX systems
  4. If available, apply the firmware upgrade in a staging/non-production environment first to validate compatibility
  5. Apply the firmware upgrade to the Experion LX controller following Honeywell's documented upgrade procedure
  6. After upgrade, verify that the CDA EpicMo protocol (55565/TCP) now has authentication enabled
  7. Confirm that unauthorized firmware download commands are no longer accepted on the affected port
  8. Validate normal operational functionality post-upgrade
Caveat DCS firmware upgrades carry inherent risk and should be thoroughly tested in a non-production environment before production deployment; coordinate upgrade window with operations team to minimize downtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experion Lx Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing20.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-30317 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