Security readout for executives and security teams
Plain-English summary
Johnson Controls Metasys SCT and SCT Pro are reported vulnerable to server-side request forgery. A remote attacker could send a crafted request that causes the product to make or forge requests toward internal systems, potentially exposing limited internal information.
Executive priority
Treat this as a moderate operational security issue. It does not have confirmed active exploitation in the supplied evidence, but building-management tooling can bridge sensitive internal networks, so exposed instances should be inventoried and remediated through vendor guidance.
Technical view
CVE-2021-36203 is CWE-918 affecting Metasys System Configuration Tool and SCT Pro, listed as all versions. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact only.
Likely exposure
Exposure is most relevant where Metasys SCT or SCT Pro is reachable over a network, especially from untrusted segments. The provided sources do not identify specific internet exposure, default configurations, or exact vulnerable releases beyond all versions.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is remotely reachable and unauthenticated by CVSS, but the documented impact is limited to confidentiality with no stated integrity or availability impact.
Researcher notes
Evidence supports SSRF-style behavior but does not include technical exploit detail, fixed versions, or mitigations. Validation should focus on asset discovery, reachability, version/support status, and whether vendor guidance has since narrowed affected releases.
Mitigation direction
- Identify all Metasys SCT and SCT Pro instances in the environment.
- Review Johnson Controls and CISA guidance for supported remediation.
- Apply only vendor-documented patches, upgrades, or mitigations for the deployed version.
- Restrict SCT/SCT Pro access to authorized management networks where feasible.
- Monitor vendor advisories for updated affected-version or remediation details.
Validation and detection
- Confirm whether SCT or SCT Pro is installed and network-accessible.
- Map access paths from user, server, and untrusted network segments.
- Check vendor advisory status against each deployed version.
- Review logs for unusual requests involving internal network destinations.
- Document unresolved exposure where no vendor fix is confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-36203 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsa-22-111-02CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.