Kantech EntrapassApplication · Johnsoncontrols

CVE-2020-9046

HIGH · 7.8 CVSS v3.1 Published 2020-05-26
Fix available
A fix is available. Upgrade to after 8.22 or later.
See remediation →
80/100
Remediation priority · High
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 all versions of Kantech EntraPass Editions could potentially allow an authorized low-privileged user to gain full system-level privileges by replacing critical files with specifically crafted files.

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

Kantech EntraPass access control software contains a local privilege escalation vulnerability where an authorized low-privileged user can replace critical system files with maliciously crafted files, achieving full system-level privileges. This appears to stem from improper file permission controls allowing file write access to sensitive executables or configurations.

MitigationImplement strict file system permissions on critical EntraPass binaries and configuration files to prevent low-privileged users from modifying them; restrict write access to authorized administrators only. Consider applying any available vendor patches for EntraPass and reviewing the privilege model.

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
Kantech EntrapassApplication
Affected:<= 8.22

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

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify EntraPass installation
    Check if Kantech EntraPass software is installed on the system. Look for EntraPass in installed programs or common installation directories.
    Affected if EntraPass is installed on the system
  2. Check installed version
    Identify the installed version of Kantech EntraPass. Compare against the affected range of <= 8.22.
    Affected if Installed version is 8.22 or lower
  3. Inspect file permissions on EntraPass binaries
    Examine file system permissions on EntraPass executable files. Verify if non-privileged users have write access to critical .exe or .dll files in the EntraPass installation directory.
    Affected if Low-privileged users can write to EntraPass executable files
  4. Inspect file permissions on configuration files
    Examine file system permissions on EntraPass configuration and data files. Check if write access is improperly granted to standard users.
    Affected if Low-privileged users can write to EntraPass configuration or sensitive data files
  5. Identify unauthorized file modification points
    Locate critical system or application files within the EntraPass directory tree that are world-writable or writable by non-admin users.
    Affected if Critical EntraPass files are writable by non-administrator accounts

A system is affected if EntraPass version 8.22 or lower is installed AND low-privileged users have write access to EntraPass executables or configuration files.

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.

From vendor data
Upgrade available Upgrade to a release after 8.22
Interim mitigation

Implement strict file system permissions on critical EntraPass binaries and configuration files to prevent low-privileged users from modifying them; restrict write access to authorized administrators only. Consider applying any available vendor patches for EntraPass and reviewing the privilege model.

Fix this in Kantech Entrapass Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9046 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9046 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