dbcve.org
Metasys Application And Data ServerApplication · Johnsoncontrols

CVE-2022-21935

HIGH · 7.5 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 10.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A vulnerability in Metasys ADS/ADX/OAS 10 versions prior to 10.1.5 and Metasys ADS/ADX/OAS 11 versions prior to 11.0.2 allows unverified password change.

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 · high confidence

A vulnerability in Metasys ADS/ADX/OAS building automation platform versions 10.x prior to 10.1.5 and 11.x prior to 11.0.2 allows unverified password changes, potentially enabling an attacker to take over user accounts without proper authentication or verification.

MitigationUpgrade Metasys ADS/ADX/OAS to version 10.1.5 or 11.0.2 or later to remediate this vulnerability.

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.1
Metasys Extended Application And Data ServerApplication
Affected:>= 10.0, <= 10.1.5= 11.0= 11.0.1
Metasys Open Application ServerApplication
Affected:>= 10.0, < 10.1.5= 11.0= 11.0.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 Metasys product type
    Locate the installed Metasys product by checking the system services, installed programs, or the web application banner. Common locations include the Windows Services list (Metasys ADS, Metasys ADX, or Metasys OAS service) or the application's login page which typically displays the product name.
    Affected if The system is running Metasys ADS, Metasys ADX, or Metasys OAS
  2. Check the installed Metasys version
    Access the Metasys system information or about page through the web interface (typically /MetasysXXX/About or through the System Diagnostics interface), or check the Windows installed programs list, registry, or product-specific configuration files for the version number.
    Affected if The version falls within these ranges: 10.0 through 10.1.5 (for ADS/ADX), 10.0 through 10.1.4 (for OAS), or versions 11.0 and 11.0.1 for any of the three products
  3. Verify the password change interface is accessible
    Check if the user password change or reset functionality is exposed through the web API or UI endpoints (such as /UserManagement/ChangePassword or similar). This can be confirmed by reviewing accessible API endpoints or attempting to access the password change mechanism without authentication.
    Affected if The password change endpoint accepts requests without requiring proper authentication or token verification

You are affected if you are running Metasys ADS, ADX, or OAS version 10.x through 10.1.5 (or 10.1.4 for OAS) or versions 11.0/11.0.1, and the password change interface is accessible without authentication verification.

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 or later
Fixed in 10.1.5
Interim mitigation

Upgrade Metasys ADS/ADX/OAS to version 10.1.5 or 11.0.2 or later to remediate this vulnerability.

Recommended fix High confidence

Metasys 10.x: upgrade to 10.1.5 or later; Metasys 11.x: upgrade to 11.0.2 or later

  1. Identify the currently installed Metasys ADS/ADX/OAS version by checking the system information or version menu
  2. For Metasys 10.x versions (10.0 through 10.1.4): Upgrade to version 10.1.5 or later
  3. For Metasys 11.x versions (11.0, 11.0.1): Upgrade to version 11.0.2 or later
  4. After upgrade, verify the system is functioning correctly and test the password change functionality
  5. Confirm the version upgrade was successful by checking the installed version
Caveat Review Johnson Controls release notes for any configuration or compatibility changes between versions before upgrading

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21935 — 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-21935 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