CVE-2019-7589
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 · uneditedA vulnerability with the SmartService API Service option exists whereby an unauthorized user could potentially exploit this to upload malicious code to the server that could be executed at system level privileges. This affects Johnson Controls' Kantech EntraPass Corporate Edition versions 8.0 and prior; Kantech EntraPass Global Edition versions 8.0 and prior.
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 confidenceThe SmartService API Service in Kantech EntraPass versions 8.0 and prior contains an authentication/authorization bypass allowing unauthenticated attackers to upload malicious files that execute with SYSTEM-level privileges, enabling complete system compromise.
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< 8.10CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify EntraPass versionCheck the installed EntraPass version through the application (Help > About) or by inspecting the installation directory for version metadataAffected if Installed version is below 8.10 (or version cannot be determined and is known to be 8.0 or prior)
-
Confirm SmartService API is enabledCheck if the SmartService API service is running on the EntraPass server. This is typically a Windows service named 'EntraPass SmartService' or similar, viewable via Services.mscAffected if SmartService API service is installed and running on the system
-
Assess network exposure of SmartService APIReview firewall rules and network configuration to determine if the SmartService API port (commonly port 9001, verify in service documentation) is accessible from untrusted networksAffected if SmartService API port is exposed to untrusted/untrusted networks or the internet
-
Inspect upload directories for suspicious filesExamine the upload directories used by the SmartService API for any unexpected or malicious files. Check application logs for unauthorized upload attemptsAffected if Unexpected files exist in upload directories or logs show unauthenticated upload activity
System is likely affected if EntraPass version is below 8.10 and the SmartService API service is enabled and network-accessible to untrusted sources.
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 · scoped8.10
Apply vendor patch when available; until then, restrict network access to the SmartService API to trusted IPs only via firewall, disable the API service if not required, and monitor for suspicious upload activity.
Entrapass version 8.10 or later
- Verify current Entrapass version by checking the application or system information
- Download Entrapass version 8.10 or later from the official Johnson Controls website or your authorized distribution channel
- Review Johnson Controls upgrade documentation and release notes before proceeding
- Backup the current Entrapass database and configuration files
- Stop all Entrapass services including the SmartService API Service
- Install version 8.10 or later following the standard upgrade procedure
- After installation, restart all Entrapass services
- Verify the SmartService API Service is running correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7589 — 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-2019-7589 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