dbcve.org
Metasys Application And Data ServerApplication · Johnsoncontrols

CVE-2022-21934

HIGH · 8.8 CVSS v3.1 Published 2022-05-06
Fix available
A fix is available. Upgrade to 10.1.5 / 11.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Under certain circumstances an authenticated user could lock other users out of the system or take over their accounts in Metasys ADS/ADX/OAS server 10 versions prior to 10.1.5 and Metasys ADS/ADX/OAS server 11 versions prior to 11.0.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authentication/authorization vulnerability in Metasys ADS/ADX/OAS building automation servers where an authenticated user can manipulate user accounts to lock other users out or hijack their sessions. The flaw allows privilege escalation within the user management subsystem.

MitigationUpgrade Metasys ADS/ADX/OAS server to version 10.1.5 or 11.0.2 or later to patch the authorization flaw.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Metasys Application And Data ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2
Metasys Extended Application And Data ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2
Metasys Open Application ServerApplication
Affected:>= 10.0, < 10.1.5>= 11.0, < 11.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Metasys product type
    Check the system for one of these components: Metasys Application and Data Server (ADS), Metasys Extended Application and Data Server (ADX), or Metasys Open Application Server (OAS). Look in Windows Programs and Features, or check the Metasys server installation directory for the installed component name.
    Affected if The system has ADS, ADX, or OAS installed as a building automation server
  2. Determine the installed version
    Open Windows Control Panel > Programs and Features, locate the Metasys component, and note the version column. Alternatively, check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Johnson Controls\Metasys\Version or look in the installation directory for a version file.
    Affected if The version matches the affected ranges: >= 10.0 and < 10.1.5, OR >= 11.0 and < 11.0.2
  3. Confirm the user management subsystem is accessible
    Log into the Metasys web interface or SMP (System Management Portal) and navigate to the User Management or Users and Roles section. Verify you can access the interface where user accounts are created, modified, or deleted.
    Affected if The user management interface is accessible with administrative credentials and the server version is within the affected range
  4. Check for unauthorized user account modifications
    Review the audit logs or security event logs on the Metasys server for any user account changes, password resets, or role modifications performed by unexpected users. Look for events indicating user lockouts or session hijacking.
    Affected if Audit logs show user account modifications that were not performed by authorized administrators, indicating exploitation of the authorization flaw

A system is affected if it runs Metasys ADS, ADX, or OAS version 10.0 through 10.1.4 or version 11.0 through 11.0.1, where the user management interface is accessible and exploitable by authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.1.5 / 11.0.2 or later
Fixed in 10.1.511.0.2
Interim mitigation

Upgrade Metasys ADS/ADX/OAS server to version 10.1.5 or 11.0.2 or later to patch the authorization flaw.

Recommended fix High confidence

Metasys ADS/ADX/OAS version 10.1.5 (for 10.x branches) or version 11.0.2 (for 11.x branches)

  1. Identify the currently installed Metasys ADS/ADX/OAS version by checking the system information or version details in the Metasys administration interface
  2. If running version 10.x: Schedule an upgrade to version 10.1.5 or later
  3. If running version 11.x: Schedule an upgrade to version 11.0.2 or later
  4. Before upgrading, perform a complete backup of the Metasys server configuration and database
  5. Review Johnson Controls Metasys upgrade documentation for any prerequisites
  6. Execute the upgrade following the vendor's official upgrade procedure
  7. After upgrade, verify that all services are running correctly
  8. Test user authentication and account management functionality to confirm the fix is working

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metasys Application And Data Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21934 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data