dbcve.org
CevasApplication · Johnsoncontrols

CVE-2021-36206

MEDIUM · 6.1 CVSS v3.1 Published 2022-10-28
Fix available
A fix is available. Upgrade to 1.01.46 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
All versions of CEVAS prior to 1.01.46 do not sufficiently validate user-controllable input and could allow a user to bypass authentication and retrieve data with specially crafted SQL queries.

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

SQL injection vulnerability in CEVAS versions prior to 1.01.46 allows attackers to bypass authentication mechanisms and retrieve unauthorized data through specially crafted SQL queries due to insufficient user input validation.

MitigationUpgrade to CEVAS version 1.01.46 or later which contains proper input validation; alternatively, implement parameterized queries/prepared statements for all database interactions to prevent SQL injection.

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
CevasApplication
Affected:< 1.01.46

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 CEVAS installation
    Locate the CEVAS application installation directory or check the software inventory/system registry for Johnson Controls CEVAS version information
    Affected if CEVAS version cannot be determined or is not listed in the system
  2. Determine installed CEVAS version
    Retrieve the version number of the installed CEVAS instance through the application's about page, version file, or system administration panel
    Affected if Installed version is < 1.01.46 or version cannot be verified
  3. Verify authentication module exposure
    Determine if the CEVAS web interface or authentication portal is accessible and exposed to network traffic
    Affected if Authentication module is accessible and version is vulnerable
  4. Check for SQL injection mitigation
    If version is confirmed < 1.01.46, examine whether parameterized queries have been implemented as a compensating control by reviewing application database interaction code or configuration
    Affected if No input validation or parameterized query implementation is found in authentication-related database code

The environment is affected if CEVAS version is confirmed to be below 1.01.46 and the authentication interface is accessible without additional compensating controls in place.

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

Upgrade to CEVAS version 1.01.46 or later which contains proper input validation; alternatively, implement parameterized queries/prepared statements for all database interactions to prevent SQL injection.

Recommended fix Moderate confidence

CEVAS version 1.01.46

  1. 1. Identify all deployed instances of CEVAS currently running versions prior to 1.01.46
  2. 2. Obtain the CEVAS version 1.01.46 or later from the official Johnson Controls distribution channel
  3. 3. Review upgrade documentation for CEVAS to understand any prerequisites
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Perform a full backup of the CEVAS application, configuration, and associated database before upgrading
  6. 6. Upgrade CEVAS to version 1.01.46 or latest available stable release
  7. 7. Verify the upgrade was successful by confirming the new version number in the application
  8. 8. Test critical functionality to ensure the upgrade did not break existing workflows
Caveat Review vendor release notes for any configuration or feature changes between your current version and 1.01.46

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

Fix this in Cevas Scoped from the published advisory
  • Consultation8.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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