dbcve.org
Metasys SystemApplication · Johnsoncontrols

CVE-2019-7593

CRITICAL · 9.1 CVSS v3.0 Published 2019-08-20
Fix available
A fix is available. Upgrade to 9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Metasys® ADS/ADX servers and NAE/NIE/NCE engines prior to 9.0 make use of a shared RSA key pair for certain encryption operations involving the Site Management Portal (SMP).

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

The vulnerability involves the use of a shared/static RSA key pair hardcoded in the Metasys system for encrypting Site Management Portal (SMP) communications. Since the same key is used across all installations, an attacker who obtains this key can decrypt sensitive communications or impersonate the SMP server, leading to complete compromise of the system's confidentiality and integrity.

MitigationUpgrade to Metasys version 9.0 or later, which implements proper per-instance key management. Until upgrade, network-segment the SMP from untrusted networks and monitor for indicators of key compromise or anomalous authentication patterns.

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 SystemApplication
Affected:< 9.0

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
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installed Metasys version
    Locate the Metasys version information in the system configuration, About dialog, or registry entries typically found under the Metasys installation directory or system information panel
    Affected if The installed version is below 9.0 (e.g., 8.x, 8.0.x, or earlier)
  2. Confirm Site Management Portal (SMP) is deployed
    Check if the SMP component is installed and configured on this Metasys installation by reviewing installed components or the system architecture documentation
    Affected if SMP is present and configured for communication with Metasis servers
  3. Locate RSA key files used for SMP encryption
    Examine the Metasys installation directory and configuration folders for certificate or key files (commonly found in security or configuration subdirectories)
    Affected if Static RSA key files exist that appear identical across multiple Metasys installations
  4. Verify key is hardcoded or shared
    Inspect the key material or configuration files for evidence of embedded RSA private keys, or compare key fingerprints with known installations to confirm they are identical
    Affected if The same RSA key pair is used across different Metasys installations or the key is embedded in application binaries/configuration

If the Metasys version is below 9.0 and the system uses a hardcoded or shared RSA key pair for SMP communications rather than unique per-instance keys, the environment is affected by CVE-2019-7593.

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

Upgrade to Metasys version 9.0 or later, which implements proper per-instance key management. Until upgrade, network-segment the SMP from untrusted networks and monitor for indicators of key compromise or anomalous authentication patterns.

Recommended fix High confidence

9.0

  1. Upgrade Metasys ADS/ADX servers to version 9.0 or later
  2. Upgrade NAE/NIE/NCE engines to version 9.0 or later
  3. After upgrade, verify that new unique RSA key pairs are being generated for SMP encryption operations
  4. Confirm the Site Management Portal is functioning correctly with the updated encryption
Caveat Review Johnson Controls upgrade documentation for any compatibility requirements or configuration changes needed when moving from versions prior to 9.0

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

Fix this in Metasys System Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing20.0 h
  • Review / QA10.0 h
74.0 hours of engineering $12,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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