Malicious firmware execution via incomplete boot verification
Published Jul 28, 2025 · Updated Aug 19, 2025
Insufficient firmware verification in Johnson Controls iSTAR Ultra 6.9.2 and earlier allows local users to execute malicious code. The boot-time integrity check omits portions of the firmware image, so attacker-modified code in those regions passes verification. High device privileges are required directly, although a separate authenticated command-injection flaw provides a network-reachable modification path; successful tampering can persist malicious controller code.
Summary
What happened
Insufficient firmware verification in Johnson Controls iSTAR Ultra 6.9.2 and earlier allows local users to execute malicious code. The boot-time integrity check omits portions of the firmware image, so attacker-modified code in those regions passes verification. High device privileges are required directly, although a separate authenticated command-injection flaw provides a network-reachable modification path; successful tampering can persist malicious controller code.
The record
- CVE
- CVE-2025-53696
- Published
- Jul 28, 2025
- Updated
- Aug 19, 2025
- Vendor
- Johnson Controls
- Product
- iSTAR Ultra
- Classifications
- CWE-494, CAPEC-452, CAPEC-638, T1601.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 28, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.9.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo