MediumCVE-2025-2522

Honeywell FIM4: Sensitive Information in Resource Not Removed Before Reuse (CVE-2025-2522)

Published 10.07.2025Sources: CVE.org

What is affected, what to do

The available sources name no fixed version. Check the vendor guidance in the references below.

Affected: Honeywell C300 PCNT02 gte 520.1..*
Honeywell C300 PCNT02 gte 530..*
Honeywell C300 PCNT05 gte 520.1..*
Honeywell C300 PCNT05 gte 530..*
Honeywell FIM4 gte 520.1..*
Honeywell FIM4 gte 530..*
Honeywell FIM8 gte 520.1..*
Honeywell FIM8 gte 530..*
Honeywell UOC gte 520.1..*
Honeywell UOC gte 530..*
Honeywell CN100 gte 520.1..*
Honeywell CN100 gte 530..*
Honeywell HCA gte 520.1..*
Honeywell HCA gte 530..*
Honeywell C300PM gte 520.1..*
Honeywell C300PM gte 530..*
Honeywell C200E gte 520.1..*
Honeywell C200E gte 530..*
Honeywell Wireless Device Manager lte 322.1..322.4
Honeywell Wireless Device Manager lte 330.1..330.3

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

6.5

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: Vendor (CNA), CVSS v3

6.5

CVSS v3

Severity Medium on the scale from 0 to 10.

Source: CVE.org

0.3 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 19.2

Show all metrics

Severity: Medium
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 45.16 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 6.5 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 6.5
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.3 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 19.2; Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 10.07.2025
CISA assessment (SSVC): Exploitation: none known · not automatable · Technical impact: partial; Source: CISA Vulnrichment, as of 10 July 2025
CWE CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect. Read in glossary: CWE-226

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

The Honeywell Experion PKS and OneWireless WDM contains Sensitive Information in Resource vulnerability in the component Control Data Access (CDA). An attacker could potentially exploit this vulnerability, leading to a Communication Channel Manipulation, which could result in buffer reuse which may cause incorrect system behavior. Honeywell also 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, FIM4, FIM8, UOC, CN100, HCA, C300PM, and C200E. The Experion PKS versions affected are 520.1 before 520.2 TCU9 HF1 and 530 before 530 TCU3. The OneWireless WDM affected versions are 322.1 through 322.4 and 330.1 through 330.3.

Source: cvelistv5, NVD (NIST)

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Honeywell	C200E	`≥ 520.1` `≥ 530`	— —
Honeywell	C300 PCNT02	`≥ 520.1` `≥ 530`	— —
Honeywell	C300 PCNT05	`≥ 520.1` `≥ 530`	— —
Honeywell	C300PM	`≥ 520.1` `≥ 530`	— —
Honeywell	CN100	`≥ 520.1` `≥ 530`	— —
Honeywell	FIM4	`≥ 530` `≥ 520.1`	— —
Honeywell	FIM8	`≥ 530` `≥ 520.1`	— —
Honeywell	HCA	`≥ 530` `≥ 520.1`	— —
Honeywell	UOC	`≥ 520.1` `≥ 530`	— —
Honeywell	Wireless Device Manager	`330.1 – ≤ 330.3` `322.1 – ≤ 322.4`	— —

Vendors and products

Weakness classes (CWE)

CWE-226Sensitive Information in Resource Not Removed Before Reuse
Base
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
Entry at MITRE CWE-226

References & sources

process.honeywell.com

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2025-2522"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-2522.svg?lang=en" alt="CVE-2025-2522 – NEOSEC Intel" height="20"></a>