Incorrect response generation during FTEB protocol processing
The Honeywell Experion PKS and OneWireless WDM contains a Deployment of Wrong Handler vulnerability in the component Control Data Access (CDA). An attacker could potentially exploit this vulnerability, leading to Input Data Manipulation, which could result in incorrect handling of packets leading to remote code execution. Honeywell recommends updating to the most recent version of Honeywell Experion PKS:520.2 TCU9 HF1 and 530.1 TCU3 HF1 and OneWireless: 322.5 and 331.1. The affected Experion PKS products are C300 PCNT02, C300 PCNT05, FIM4, FIM8, UOC, CN100, HCA, C300PM, and C200E. The Experion PKS versions affected are from 520.1 through 520.2 TCU9 and from 530 through 530 TCU3. The OneWireless WDM affected versions are 322.1 through 322.4 and 330.1 through 330.3.
- Published
- Jul 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-430
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Honeywell
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Honeywell). Independent of NVD's CPE analysis and usually ahead of it.
Honeywell C200E
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell C300 PCNT02
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell C300 PCNT05
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell C300PM
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell CN100
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell FIM4
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell FIM8
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell HCA
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell UOC
- 520.1 and later · up to and including 520.2 TCU9affected · semver
- 530 and later · up to and including 530 TCU3affected · semver
Honeywell Wireless Device Manager
- 322.1 and later · up to and including 322.4affected · semver
- 330.1 and later · up to and including 330.3affected · semver
Same product
honeywell: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-2523Lack of buffer clearing before reuse may result in incorrect system behavior.37Monitor
- CVE-2025-2521Lack of indexes’ validation against buffer borders leads to remote code execution.34Monitor
- CVE-2025-3947Integer underflow during processing of short network packets in CDA FTEB responder32Monitor
- CVE-2025-2520Dereferencing of an uninitialized pointer leads to denial of service.30Monitor
- CVE-2025-2522Lack of buffer clearing before reuse may result in incorrect system behavior.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
CWE-430 · Deployment of Wrong HandlerCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.