Johnson Controls ICS
CVE-2025-61740
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network foothold
-
DeliveryCraft spoofed source packets
-
ExploitDevice fails to verify origin
-
ExecutionPush config change or trigger DoS
-
ImpactDevice compromised or unavailable
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Exploitation requires the attacker to be on the same adjacent/Layer-2 network segment as the device (AV:A) - the flaw is not exploitable across the routed internet. The core condition is that the device does not verify the source of inbound packets (CWE-346 origin validation failure), allowing spoofed packets to be accepted. No authentication (PR:N) and no user interaction (UI:N) are needed, and default configurations appear affected per the description. LIMITING FACTORS: the adjacent-network requirement means the attacker must already have access to the local/management network, which confines realistic exploitation to insiders or attackers who have breached the facility network; the specific affected Johnson Controls product/version must also be present. |
| Impact | The input CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) describes a low-complexity, unauthenticated attack reachable only from an adjacent network segment, yielding high integrity impact (VI:H, device configuration modification) with lower confidentiality and availability impact - consistent with the CWE-346 origin-validation / packet-source-spoofing root cause. This is a genuine but situational priority: the integrity impact and lack of authentication are serious, but the adjacent-network vector (not internet-routable) and the CISA ICS advisory context substantially narrow real-world reach. The EPSS score is very low (0.13%, 3rd percentile) and there is no CISA KEV listing and no public POC, so all exploitation signals point to no active or imminent widespread exploitation - the severity is driven by potential impact, not by observed activity. CONFLICT TO NOTE: the only descriptive tag is 'Information Disclosure', yet the description and the vector (VI:H, VA:L, VC:L) center on configuration modification and denial-of-service, not disclosure - verify the primary impact category with the Johnson Controls advisory. The specific affected product and versions are not provided in this input and must be confirmed from the vendor/CISA advisories. |
| Exploit ScenarioDerived | An attacker positioned on the same (adjacent) network segment as a Johnson Controls device sends spoofed or forged packets that the device fails to validate the origin of (CWE-346). Because no authentication or user interaction is required, the attacker can push unauthorized configuration changes to the device or force it into a denial-of-service state. No public exploit code is known, so exploitation would require custom packet crafting against the specific protocol. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Packet-source validation failure in Johnson Controls ICS devices on an adjacent network segment allows unauthenticated attackers to spoof traffic, potentially modifying device configuration or causing denial of service. The flaw is CWE-346 (origin validation error), requires Layer-2 adjacency (AV:A), and needs no user interaction. No public exploit code was identified at time of analysis; EPSS is 0.13% (3rd percentile), and KEV status is not indicated.
RemediationAI
Apply the fixed firmware/software version listed in the Johnson Controls security advisory and CISA ICSA-25-350-02; an exact fix version was not included in the provided data, so confirm the model-specific release before upgrading. Until patched, place affected devices on a dedicated management VLAN, restrict Layer-2 access with 802.1X and port-level ACLs, and disable unused discovery/management protocols to reduce spoofable attack surface. Enable ingress filtering/unicast RPF on upstream Layer 3 devices where topology permits, and monitor for source-spoofed packets. Trade-offs: stricter segmentation and 802.1X can disrupt BAS integrations and legacy devices that lack supplicant support; uRPF can drop legitimate asymmetric traffic; disabling protocols may break required integrations. No public exploit was identified at time of analysis, but the low attack complexity and unauthenticated adjacent-network path warrant prompt patching.
Affected ProductsAI
Affected products are the Johnson Controls ICS devices enumerated in CISA advisory ICSA-25-350-02 and the Johnson Controls trust-center security advisory (https://www.cisa.gov/news-events/ics-advisories/icsa-25-350-02; https://www.johnsoncontrols.com/trust-center/cybersecurity/security-advisories). The input data does not include CPE strings, model names, or firmware version ranges, so the authoritative affected list should be read from those advisories. The vulnerable condition is present where the device accepts inbound packets without source validation and is reachable from an adjacent network segment; deployments on isolated management VLANs still need the vendor-listed fix.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-346 covers improper origin validation: software accepts packets without confirming the sender is trusted. Here the Johnson Controls device does not verify packet source, so an attacker on the same Layer-2/adjacent segment can inject spoofed traffic. The CVSS 4.0 vector AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L shows no authentication or interaction, high integrity impact, and limited confidentiality/availability; the independent CVSS 3.1 assessment (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) is consistent. No CPE strings or protocol/port details were supplied, and the public tag 'Information Disclosure' understates the assessed configuration-modification risk; exact affected models/versions must be taken from the CISA and Johnson Controls advisories.
Know when Johnson Controls 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:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:L/SA:N
AV:A and AC:L/PR:N/UI:N reflect unauthenticated adjacent-network packet spoofing with no origin check; I:H for config modification, C:L and A:L for limited disclosure and DoS.
Primary rating from Vendor (jci).
CVSS VectorVendor: jci
DescriptionCVE.org
Authentication issue that does not verify the source of a packet which could allow an attacker to create a denial-of-service condition or modify the configuration of the device.
Executive ViewAI
Johnson Controls ICS devices are exposed to a high-severity origin-validation flaw that could allow an attacker on an adjacent network segment to spoof traffic and alter device configuration or disrupt operations. Because no vendor-released patch is identified, leadership should treat this as an operational risk to building and OT environments and prioritize segmentation, monitoring, and vendor engagement.
Restrict Layer-2 adjacency to trusted OT segments; enforce port security, DHCP snooping and ARP inspection where supported, ACLs, and 802.1X where feasible; monitor for spoofed traffic and unauthorized configuration changes; engage Johnson Controls for patch timeline and hardening guidance.
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 Johnson Controls
View allHard-coded cryptographic key in Johnson Controls EasyIO FS32 building automation controllers before firmware 3.0b63 perm
Cleartext transmission of sensitive information in Johnson Controls EasyIO NEO (all versions before 3.3b25) lets an atta
Server-Side Request Forgery in Johnson Controls CCure 9000 and the victor application server (versions 2.9 through 3.0)
Privilege management weakness in Johnson Controls victor Web (video management client) on Windows lets a high-privileged
External control of file name or path (CWE-73) in Johnson Controls Airwall before version 4.1 enables file manipulation
Hard-coded cryptographic key exposure in Johnson Controls Airwall before version 4.1 enables local attackers to conduct
Cleartext credential exposure in Johnson Controls Simplex Incident Manager / Autocall Fire Administrator (all versions b
OS command injection in Johnson Controls devices can allow a low-privilege authenticated remote attacker to execute arbi
Command injection in certain Johnson Controls devices allows a low-privilege authenticated attacker to execute arbitrary
Hard-coded cryptographic key material embedded in Johnson Controls ADVMS builds prior to 3.10 lets a locally authenticat
Use of a hard-coded cryptographic key in Johnson Controls Kantech EntraPass before 9.20 enables a padding oracle crypto
Information disclosure in Johnson Controls Easy IO Neo versions before 3.3b63 allows an authenticated high-privileged at
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB