CVE-2025-3944

7.2 HIGH

📋 TL;DR

This vulnerability allows attackers to manipulate files on systems running vulnerable versions of Tridium Niagara Framework or Niagara Enterprise Security on QNX. It affects organizations using these building automation and security management platforms with incorrect permission assignments for critical resources.

💻 Affected Systems

Products:
  • Tridium Niagara Framework
  • Tridium Niagara Enterprise Security
Versions: Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security: before 4.14.2, before 4.15.1, before 4.10.11
Operating Systems: QNX
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations on QNX operating systems. Other platforms are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing unauthorized file modification, configuration changes, or installation of malicious software on building automation systems.

🟠

Likely Case

Unauthorized file access and modification leading to system instability, data corruption, or privilege escalation.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls preventing exploitation attempts.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires some level of access to the system. No public exploit code has been identified at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11

Vendor Advisory: https://docs.niagara-community.com/category/tech_bull

Restart Required: Yes

Instructions:

1. Download the appropriate patch version from Tridium/Honeywell. 2. Backup current configuration and data. 3. Apply the patch following vendor instructions. 4. Restart the Niagara service or system. 5. Verify the patch was applied successfully.

🔧 Temporary Workarounds

Restrict File Permissions

linux

Manually review and tighten file permissions on critical Niagara directories and files

chmod 750 /path/to/niagara/directories
chown niagara:niagara /path/to/niagara/files

Network Segmentation

all

Isolate Niagara systems from untrusted networks and implement strict firewall rules

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach Niagara systems
  • Monitor file system changes and unauthorized access attempts on Niagara directories

🔍 How to Verify

Check if Vulnerable:

Check the Niagara version via the web interface or configuration files. Compare against affected versions listed in the advisory.

Check Version:

Check the NiagaraAbout.bog file or use the web interface at http://[niagara-ip]/station/version

Verify Fix Applied:

Verify the installed version matches the patched versions (4.14.2u2, 4.15.u1, or 4.10u.11) and test file permission assignments.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized file access attempts in Niagara logs
  • File permission changes in system logs
  • Unexpected file modifications in critical directories

Network Indicators:

  • Unusual network traffic to Niagara systems from unauthorized sources
  • Multiple failed authentication attempts followed by file access

SIEM Query:

source="niagara_logs" AND (event="file_access" OR event="permission_change") AND user NOT IN ["authorized_users"]

🔗 References

📤 Share & Export