Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain network-adjacent position on BMS segment
-
ExploitIntercept controller communication path (MITM)
-
ExecutionCapture cleartext sensitive data
-
ImpactReuse harvested credentials/data against controller
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V12 - Secure Communication Transport encryption
|
| Exploitation Conditions | Exploitation requires the attacker to achieve a man-in-the-middle position on the network path used by EasyIO NEO (versions before 3.3b25), because sensitive information is transmitted without encryption (CWE-319). Limiting factors per the CVSS 4.0 vector: HIGH attack complexity (AC:H) and a present attack requirement (AT:P) mean the attacker must control or intercept the communication channel; low privileges (PR:L) are needed; and user/passive interaction (UI:P) is required, so a victim-side transmission must occur for sensitive data to be captured. This is not remote-unauthenticated exploitation against default configurations - it is gated by network positioning and interaction. |
| Impact | This is a moderate, context-dependent risk rather than a top-tier emergency. The only severity signal provided is a vendor-supplied (jci/Johnson Controls) CVSS 4.0 base score of 7.3 with vector AV:N/AC:H/AT:P/PR:L/UI:P - meaning that while the vector is network-reachable, exploitation carries HIGH attack complexity (AC:H), a specific attack requirement (AT:P), requires low-level privileges (PR:L), and depends on user/passive interaction (UI:P). These modifiers collectively indicate a non-trivial, situational attack - consistent with a man-in-the-middle (CWE-319 cleartext transmission) scenario where the attacker must already occupy a privileged network position on the path between victim endpoints. No EPSS score, no CISA KEV listing, and no proof-of-concept were provided, so there is no public exploit identified at time of analysis and no evidence of active or widespread exploitation. Note a tension worth flagging: AV:N implies remote reachability, but a cleartext/MITM flaw realistically requires network-adjacent interception positioning, which is why AC:H is appropriate - the 'network' vector does not mean trivial internet-wide exploitation. Given EasyIO NEO is a niche building-automation/HVAC controller rather than ubiquitous software, this should be prioritized by operators of affected OT/BMS environments but does not warrant emergency cross-industry response. |
| Exploit ScenarioDerived | An attacker who has gained a foothold on the same operational-technology/building-automation network segment as an EasyIO NEO controller positions themselves as a man-in-the-middle on the communication path. Because sensitive information is transmitted in cleartext, the attacker passively intercepts or actively relays traffic to capture credentials or configuration data exchanged with the controller. No public exploit code was identified, and the attack requires both a privileged network position and victim-side interaction, limiting opportunistic use. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Cleartext transmission of sensitive information in Johnson Controls EasyIO NEO (all versions before 3.3b25) lets an attacker who has already achieved a man-in-the-middle position on the network path read data the controller exchanges without encryption. It is rated 7.3 under CVSS 4.0 and mapped to CWE-319, but exploitation is gated rather than trivial: the assessed vector (AV:N/AC:H/PR:L/UI:R, consistent with the CVSS 4.0 AC:H, AT:P, PR:L, UI:P values) requires channel control or interception, low privileges on the attacker side, and a victim-side transmission to occur. There is no CISA KEV listing and no public exploit identified at time of analysis, making this a moderate, context-dependent risk rather than an emergency, and impact is primarily confidentiality loss with limited integrity/availability effects.
RemediationAI
The primary fix is to upgrade EasyIO NEO firmware to 3.3b25 or later, the version boundary the vendor advisory uses to delimit the affected range ("before 3.3b25"), and to verify the installed build on each controller after flashing; consult the Johnson Controls advisory at https://www.johnsoncontrols.com/trust-center/cybersecurity/security-advisories for the authoritative release notes. Where immediate firmware updates are not possible, the effective compensating control is to remove the attacker's ability to reach the man-in-the-middle position: place NEO controllers and their management/engineering workstations on a dedicated, tightly firewalled OT VLAN, and tunnel all management, engineering and telemetry traffic through an encrypted overlay (IPsec, WireGuard or an equivalent VPN/SSH tunnel) so the cleartext hop is never observable. The trade-off is added latency and complexity in the OT path plus the need to manage tunnel keys on constrained devices; additionally, disable or restrict untrusted management interfaces (for example, block direct HTTP/web access from anything other than an engineering jump host) and enable port security, DHCP snooping and dynamic ARP inspection at the access layer to blunt the spoofing techniques used to obtain the interception position, accepting that legacy switches may not support these features. Because a MITM requires physical or logical adjacency, minimizing flat L2 domains and auditing for rogue devices or mirrored ports is a high-value secondary step; monitoring for replayed or re-used credentials captured from cleartext sessions should accompany any interim control until 3.3b25 is deployed.
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
EasyIO NEO is a Johnson Controls building-automation/edge controller platform (CPE cpe:2.3:a:johnson_controls:easyio_neo:*:*:*:*:*:*:*:*), the kind of device that sits between field equipment and supervisory building management systems and therefore handles credentials, configuration, telemetry and control traffic. The root cause is CWE-319, Cleartext Transmission of Sensitive Information: rather than a memory-safety or injection bug, the product sends sensitive data over a channel that is not protected by transport encryption, so any party able to observe or relay that traffic can recover it. In OT/IoT/building-automation networks this is typically reached through ARP or DNS spoofing, rogue access points, mirror ports, or compromised intermediate switches/routers; the HIGH attack complexity and present attack requirement in the CVSS 4.0 vector reflect that this positioning is a prerequisite, not something the vulnerability itself provides. Because the resulting exposure is disclosure (plus possible downstream integrity/availability effects through reuse of recovered secrets), the weakness is best addressed by adding transport-layer protection (TLS/VPN/IPsec) and by network segmentation rather than by input validation.
Know when Easyio Neo 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:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H
MITM interception of cleartext data needs a privileged network position (AC:H) and a victim transmission (UI:R); primary impact is confidentiality (C:H) with limited integrity tampering and no availability impact.
Primary rating from Vendor (jci).
CVSS VectorVendor: jci
Lifecycle Timeline
2DescriptionCVE.org
- Cleartext Transmission of Sensitive Information vulnerability in Johnson Controls EasyIO NEO allows - Man In the Middle Attack.
This issue affects EasyIO NEO: before 3.3b25.
Executive ViewAI
Johnson Controls EasyIO NEO building controllers running any version before 3.3b25 exchange sensitive data across the network without encryption, so an attacker who has already established a man-in-the-middle position on that path can read it. Exploitation is gated rather than trivial - it requires the attacker to already hold a position of low privilege on the channel plus a victim-side transmission - and there is no public exploit identified at time of analysis, making this a context-dependent confidentiality risk rather than an emergency. Leadership should care because these controllers typically sit in building automation and OT environments where unencrypted traffic reaches supervisory systems that manage physical facilities, and no vendor-released patch has been identified.
No vendor-released patch identified at time of analysis. Interim mitigations: isolate EasyIO NEO controllers on a dedicated, segmented OT VLAN restricted to explicitly authorized hosts; replace cleartext communication with encrypted and authenticated transport (IPsec, TLS, or VPN) between controller and supervisory system; enforce port security and 802.1X on access switches; remove or encrypt remote-access paths to the controllers; and monitor OT segments for ARP spoofing and other man-in-the-middle activity.
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.
EUVD-2026-91074
GHSA-7qm5-3w7w-vwh7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB