dbcve.org
Experion ServerApplication · Honeywell

CVE-2023-25078

HIGH · 7.5 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to after 520.2tcu2 or later.
See remediation →
84/100
Remediation priority · High
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
Server or Console Station DoS due to heap overflow occurring during the handling of a specially crafted message for a specific configuration operation.  See Honeywell Security Notification for recommendations on upgrading and versioning.

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 confidence

A heap overflow vulnerability in Honeywell security products allows remote attackers to cause denial of service by sending specially crafted messages targeting a specific configuration operation. The vulnerability corrupts heap memory during message handling, leading to server or console station crash.

MitigationApply vendor-provided patches from the Honeywell Security Notification and restrict network access to the affected configuration interface until remediation is complete.

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 ServerApplication
Affected:>= 501.1, <= 501.6hf8>= 510.1, <= 510.2hf12>= 511.1, <= 511.5tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2
Experion StationApplication
Affected:>= 501.1, <= 501.6hf8>= 510.1, <= 510.2hf12>= 511.1, <= 511.5tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2
Engineering StationApplication
Affected:>= 510.1, <= 511.tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2
Direct StationApplication
Affected:>= 510.1, <= 511.tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed Honeywell product
    Locate the product name in the system inventory, Control Panel, or installed programs list. Look for Honeywell Experion Server, Honeywell Experion Station, Honeywell Engineering Station, or Honeywell Direct Station.
    Affected if The product is one of the four affected products listed in the CVE.
  2. Determine the installed version
    Check the product's About section, version information in the software, or look for version files in the installation directory. Common locations include the help menu, system information panel, or installation logs.
    Affected if A version number is found that can be compared against the affected ranges.
  3. Compare version against affected ranges
    Match the installed version number to the affected ranges provided: Experion Server/Station: 501.1-501.6hf8, 510.1-510.2hf12, 511.1-511.5tcu3, 520.1-520.1tcu4, 520.2-520.2tcu2. Engineering Station/Direct Station: 510.1-511.tcu3, 520.1-520.1tcu4, 520.2-520.2tcu2.
    Affected if The installed version falls within any of the listed affected version ranges.
  4. Check network exposure of configuration interface
    Review firewall rules and network ACLs to determine if the configuration service port (typically port 5550 or similar management ports) is exposed to untrusted networks. Use netstat or firewall configuration tools to list open ports and their sources.
    Affected if The configuration interface is accessible from untrusted networks, making remote exploitation possible.

A user is affected if they have any of the four Honeywell products installed with a version number that falls within the specified affected ranges and the configuration interface is network-accessible.

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
Upgrade available Upgrade to a release after 520.2tcu2
Interim mitigation

Apply vendor-provided patches from the Honeywell Security Notification and restrict network access to the affected configuration interface until remediation is complete.

Fix this in Experion Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25078 — 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-2023-25078 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