Experion ServerApplication · Honeywell

CVE-2023-24474

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
Experion server may experience a DoS due to a heap overflow which could occur when handling a specially crafted message

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 Experion server allows remote attackers to cause denial of service by sending a specially crafted message. The heap overflow occurs during message handling, potentially corrupting memory and crashing the service.

MitigationApply vendor-supplied security patches for Experion. If no patch is available, implement network segmentation and input filtering to limit exposure to untrusted messages.

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.5tcu3>= 520.1, <= 520.1tcu4>= 520.2, <= 520.2tcu2
Direct StationApplication
Affected:>= 510.1, <= 511.5tcu3>= 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 installed Honeywell product
    Check the Control Panel Programs list or look for Honeywell Experion entries in Add/Remove Programs to determine if Experion Server, Experion Station, Engineering Station, or Direct Station is installed.
    Affected if Any of the four listed products are installed.
  2. Find the installed version number
    Open the Honeywell software and navigate to Help > About, or check the Windows Add/Remove Programs panel for the version number displayed there.
    Affected if The displayed version falls within any of the affected ranges: 501.1 to 501.6hf8, 510.1 to 510.2hf12, 511.1 to 511.5tcu3, 520.1 to 520.1tcu4, or 520.2 to 520.2tcu2.
  3. Confirm network exposure of Experion services
    Check if the Experion server or station has open network listeners on typical OPC/HTTPS ports (for example, ports 443, 4444, 5555, or custom ports configured during installation) using netstat -an or a network scanner.
    Affected if The Experion service is listening on accessible network interfaces and accepts remote connections.
  4. Verify if the vulnerability trigger is reachable
    Review firewall rules and network segmentation to confirm whether untrusted network segments can send messages to the Experion message handling service.
    Affected if The service is reachable from network segments that contain untrusted or external systems.

You are affected if any Experion Server, Station, Engineering Station, or Direct Station version matches the affected ranges AND the service is network-accessible to handle the specially crafted messages.

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-supplied security patches for Experion. If no patch is available, implement network segmentation and input filtering to limit exposure to untrusted messages.

Fix this in Experion Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24474 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