CVE-2021-36202
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 · uneditedServer-Side Request Forgery (SSRF) vulnerability in Johnson Controls Metasys could allow an authenticated attacker to inject malicious code into the MUI PDF export feature. This issue affects: Johnson Controls Metasys All 10 versions versions prior to 10.1.5; All 11 versions 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 · high confidenceServer-Side Request Forgery (SSRF) in Johnson Controls Metasys MUI PDF export feature allows authenticated attackers to manipulate the server into making arbitrary requests, potentially accessing internal resources or services. The vulnerability exists in Metasys versions prior to 10.1.5 and 11.0.2.
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>= 10.0, < 10.1.5>= 11.0, < 11.0.2>= 10.0, < 10.1.5>= 11.0, < 11.0.2>= 10.0, < 10.1.5>= 11.0, < 11.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Metasys product and versionLocate the installed version of Johnson Controls Metasys (Application And Data Server, Extended Application And Data Server, or Open Application Server) using the system inventory, software registry, or Metasys system information interfaceAffected if The installed version is 10.0 through 10.1.4 (inclusive) or 11.0 through 11.0.1 (inclusive)
-
Confirm the product typeVerify which Metasys variant is deployed: Application And Data Server (ADS), Extended Application And Data Server (EADS), or Open Application Server (OAS)Affected if Any of these three product types are running and the version falls within the affected ranges
-
Check MUI PDF export feature availabilityDetermine if the MUI (Metasys User Interface) PDF export functionality is accessible to authenticated users through the web interface or APIAffected if The PDF export feature is enabled and accessible to users (exploitation requires authentication, so any authenticated user access to this feature indicates potential exposure)
The environment is affected if the installed Metasys product (ADS, EADS, or OAS) is version 10.0 through 10.1.4 or version 11.0 through 11.0.1 and the MUI PDF export feature is available to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.1.511.0.2
Upgrade to Metasys version 10.1.5 or 11.0.2 or later to patch the vulnerability. If immediate patching is not possible, restrict access to the PDF export functionality to trusted users only and monitor for suspicious outbound requests.
Version 10.1.5 for 10.x branches; Version 11.0.2 for 11.x branches
- 1. Identify the current Metasys version (Application and Data Server, Extended ADX, or Open Application Server) by checking the system information in the Metasys administration interface
- 2. For systems running version 10.0.x through 10.1.4: Plan upgrade to version 10.1.5 or later
- 3. For systems running version 11.0.x through 11.0.1: Plan upgrade to version 11.0.2 or later
- 4. Review Johnson Controls Metasys upgrade documentation and release notes for version 10.1.5 or 11.0.2 as applicable
- 5. Create a full backup of the current Metasys system configuration and database
- 6. Test the upgrade in a non-production environment first to verify compatibility with existing integrations
- 7. Schedule maintenance window for the production upgrade
- 8. Perform the upgrade following Johnson Controls official upgrade procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-36202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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