CVE-2022-21934
📋 TL;DR
This vulnerability in Metasys building automation servers allows authenticated users to lock out other users or take over their accounts. It affects Metasys ADS/ADX/OAS servers version 10 before 10.1.5 and version 11 before 11.0.2. Attackers need valid credentials to exploit this authentication flaw.
💻 Affected Systems
- Metasys ADS Server
- Metasys ADX Server
- Metasys OAS Server
📦 What is this software?
Metasys Application And Data Server by Johnsoncontrols
View all CVEs affecting Metasys Application And Data Server →
Metasys Application And Data Server by Johnsoncontrols
View all CVEs affecting Metasys Application And Data Server →
Metasys Extended Application And Data Server by Johnsoncontrols
View all CVEs affecting Metasys Extended Application And Data Server →
Metasys Extended Application And Data Server by Johnsoncontrols
View all CVEs affecting Metasys Extended Application And Data Server →
Metasys Open Application Server by Johnsoncontrols
⚠️ Risk & Real-World Impact
Worst Case
An attacker with valid credentials could take over administrative accounts, disrupt building operations, and potentially gain control of critical building systems.
Likely Case
Malicious insiders or compromised accounts could lock legitimate users out of the system, causing operational disruption and requiring manual account recovery.
If Mitigated
With proper access controls and monitoring, impact is limited to temporary account lockouts that can be quickly remediated by administrators.
🎯 Exploit Status
Requires authenticated access but likely simple to exploit once credentials are obtained.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version 10.1.5 or later for v10, Version 11.0.2 or later for v11
Vendor Advisory: https://www.johnsoncontrols.com/cyber-solutions/security-advisories
Restart Required: Yes
Instructions:
1. Download patches from Johnson Controls support portal. 2. Backup system configuration. 3. Apply patch following vendor instructions. 4. Restart affected servers. 5. Verify patch installation and functionality.
🔧 Temporary Workarounds
Restrict User Account Access
allLimit user permissions to minimum required and implement strict access controls
Implement Account Lockout Policies
windowsConfigure account lockout after failed attempts to prevent brute force attacks
🧯 If You Can't Patch
- Isolate vulnerable systems from untrusted networks and implement strict network segmentation
- Implement multi-factor authentication and monitor for suspicious account activity
🔍 How to Verify
Check if Vulnerable:
Check server version in Metasys System Configuration or About dialog. Compare against vulnerable versions.
Check Version:
Check via Metasys UI or consult system documentation for version verification commands
Verify Fix Applied:
Verify version shows 10.1.5 or higher for v10, or 11.0.2 or higher for v11. Test user account functionality.
📡 Detection & Monitoring
Log Indicators:
- Multiple failed login attempts followed by successful login
- Unusual account lockout events
- User account modifications from unexpected sources
Network Indicators:
- Authentication traffic patterns showing account takeover attempts
- Unusual administrative access from non-standard locations
SIEM Query:
source="metasys" AND (event_type="account_lockout" OR event_type="user_modify") AND user!="admin"