Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify reachable EasyIO FS32 device
-
ExploitExtract hard-coded key from firmware
-
ExecutionDecrypt protected embedded data
-
ImpactRetrieve sensitive secrets/credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | Exploitation requires network reachability to an EasyIO FS32 controller running a firmware version before 3.0b63, plus the ability to obtain the hard-coded cryptographic key - which is embedded identically in the product's firmware and recoverable once from any device or firmware image. No authentication or user interaction is indicated by the CVSS vector (PR:N/UI:N). Limiting factors: EasyIO FS32 is a building-automation/OT device typically deployed on segmented or non-internet-facing networks, so practical reach often depends on first gaining access to the building/management network; the impact is retrieval of embedded sensitive data rather than direct device takeover. |
| Impact | This is a genuinely high-priority flaw, though the headline signals warrant scrutiny. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated exploitation, and CWE-321 (Use of Hard-coded Cryptographic Key) is a reliable, repeatable weakness class - once the embedded key is extracted from one device or firmware image, it is identical across every deployed unit, which is why such flaws rank as high real-world risk despite being OT/building-automation products. The CVSS 4.0 vector carries E:P (Proof-of-Concept) exploit maturity, indicating demonstrated exploitability rather than mere theory, but there is NO CISA KEV listing and NO EPSS score in the provided data, so active, widespread exploitation is NOT established. The vendor-assigned impact of VC:H/VI:H/VA:H AND subsequent-system SC:H/SI:H/SA:H appears inflated for a weakness whose stated effect is only 'Retrieve Embedded Sensitive Data' - that description supports a strong confidentiality impact but does not clearly justify high integrity, availability, or a scope change to downstream systems; this discrepancy should be verified with Johnson Controls. Net: a real priority for anyone running EasyIO FS32 (a patch exists and should be applied), but the 9.3 score likely overstates integrity/availability impact relative to the described confidentiality disclosure. |
| Exploit ScenarioDerived | An attacker extracts the hard-coded cryptographic key from EasyIO FS32 firmware (which is shared across all units) and uses it to decrypt or retrieve sensitive embedded data - such as credentials or configuration secrets - from any reachable device over the network. Because the CVSS vector indicates no authentication and low complexity, and the vector carries E:P proof-of-concept maturity, a working technique is demonstrable, though no public exploit is confirmed in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 01, 2026
Hard-coded cryptographic key in Johnson Controls EasyIO FS32 building automation controllers before firmware 3.0b63 permits unauthenticated remote retrieval of embedded sensitive data, as the identical key is embedded in firmware and recoverable from any device or firmware image. Network reachability to the controller is required, and because these OT devices are often segmented, practical exploitation may depend on prior access to the building-management network. No public exploit identified at time of analysis, and the vendor has released firmware 3.0b63 to remove the hard-coded key; our independent assessment rates the confidentiality-only impact at CVSS 3.1 7.5 despite the record's CVSS 4.0 score of 9.3.
Earlier versions of this analysis (1)
Johnson Controls EasyIO FS32 controllers running firmware earlier than 3.0b63 embed a hard-coded cryptographic key that lets attackers recover sensitive data stored or transmitted by the device. Because the key is static and shared across units, once it is extracted from one firmware or device image it can be reused against any vulnerable FS32 installation, and the vendor's CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) scores 10.0, meaning no authentication or user interaction is required and the flaw is deterministic rather than probabilistic. The practical barrier is not exploitation difficulty but the prerequisite of obtaining the firmware or device image to reverse-engineer the key; no public proof-of-concept or confirmed in-the-wild exploitation was identified at time of analysis, though a vendor advisory exists and the assigned severity warrants urgent patching.
RemediationAI
Update EasyIO FS32 firmware to version 3.0b63 or later, which is the vendor-released fixed version (vendor advisory: https://www.johnsoncontrols.com/trust-center/cybersecurity/security-advisories). If immediate upgrading is not possible, place affected controllers on an isolated building-automation VLAN or behind a firewall that permits only necessary management traffic; because the device is an OT controller, this may interrupt remote engineering access and centralized monitoring, so schedule a maintenance window. Restrict network reachability to the controller's management and data interfaces to trusted hosts, and monitor for anomalous outbound data retrieval or access attempts. Because the hard-coded key is embedded identically in the firmware, rotating credentials alone will not remove the exposure; replacing or updating firmware is the only definitive fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-321 (Use of Hard-coded Cryptographic Key) is the root cause class here: the EasyIO FS32, a building automation controller, embeds the same cryptographic key across devices in firmware before 3.0b63. An attacker who can reach the controller over the network can obtain or leverage that key to decrypt or retrieve embedded sensitive data. The CPE cpe:2.3:a:johnson_controls:easyio_fs32:*:*:*:*:*:*:*:* identifies the affected product line. The provided CVSS 4.0 vector (9.3) reflects high confidentiality, integrity, and availability impact in the generic record, but our independent assessment using CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) scores 7.5 because exploitation yields embedded sensitive data disclosure rather than code execution, device takeover, or persistence. The assessment notes the key is embedded identically in firmware and can be recovered once from any device or firmware image, so a single exposed unit can compromise the key material for all affected devices. No authentication or user interaction is indicated by the assessed vector (PR:N/UI:N).
Know when Easyio Fs32 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P
Hard-coded key enables remote unauthenticated retrieval of sensitive data, so AV:N/AC:L/PR:N with C:H; description implies confidentiality only, so I:N/A:N against vendor's all-high.
Primary rating from Vendor (jci).
CVSS VectorVendor: jci
Lifecycle Timeline
3DescriptionCVE.org
: Use of Hard-coded Cryptographic Key vulnerability in Johnson Controls EasyIO FS32 allows : Retrieve Embedded Sensitive Data.
This issue affects EasyIO FS32: before 3.0b63.
Executive ViewAI
Johnson Controls EasyIO FS32 building automation controllers used across our facilities contain a hard-coded cryptographic key that could allow retrieval of sensitive embedded data by anyone with network access to the building-management network. With no public exploit identified at time of analysis and a vendor-released patch (firmware 3.0b63) available, the immediate risk is manageable, but unpatched controllers represent a persistent exposure to credential theft and potential lateral movement within OT environments. Leadership should prioritize firmware upgrades and validate network segmentation to protect building systems and the data they hold.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Easyio Fs32
View allOS command injection in Johnson Controls EasyIO FS32 building-automation controller firmware before 3.0b63 allows an att
Information disclosure and availability impact in Johnson Controls EasyIO FS32 building-automation controllers (firmware
OS command injection in Johnson Controls EasyIO FS32 building-automation controllers running firmware before 3.0b63 allo
Authentication abuse in Johnson Controls EasyIO FS32 building-automation controllers running firmware earlier than 3.0b6
Johnson Controls EasyIO FS32 building-automation controllers running firmware before 3.0b63 expose a file/path-handling
Hard-coded credentials in Johnson Controls EasyIO FS32 firmware before 3.0b63 allow an attacker with adjacent-network ac
EUVD-2026-91069
GHSA-w2h3-qvv9-248h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB