CVE-2018-18630
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 was found in McKesson Cardiology product 13.x and 14.x. Insecure file permissions in the default installation may allow an attacker with local system access to execute unauthorized arbitrary code.
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 vulnerability involves insecure file permissions in the default installation of McKesson Cardiology versions 13.x and 14.x. An attacker with local system access could exploit overly permissive file access control lists (ACLs) to modify executable files or DLLs, potentially leading to arbitrary code execution with elevated privileges.
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>= 12.0, <= 12.2= 11.0= 13.0= 14.0= 14.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify McKesson Cardiology installation and versionLocate the McKesson Cardiology installation directory (commonly under C:\Program Files\McKesson or C:\McKesson). Check for subdirectories named "Cardiology" or "Horizon Cardiology". Look for version information in the directory properties, a version.txt file, or check the file properties of main executables (such as cardiology.exe or hzcardio.exe).Affected if The installed version matches 11.0, 12.0 through 12.2, 13.0, 14.0, or 14.1.0.
-
Verify file permissions on the installation directoryRight-click the main McKesson Cardiology installation folder, select Properties, then the Security tab. Examine the list of users/groups with access. Pay particular attention to entries such as "Everyone", "Users", or "Authenticated Users" that may have Write or Modify permissions.Affected if Users other than Administrators or designated service accounts have Write, Modify, or Full Control permissions on the installation directory.
-
Check executable and DLL file permissionsNavigate to the bin or executable subfolder within the Cardiology installation directory. Right-click on .exe and .dll files, open Properties, then Security. Verify whether unauthorized users or groups have Write or Modify rights to these files.Affected if Executable files (.exe) or dynamic link libraries (.dll) allow Write or Modify access for non-admin users.
-
Inspect ACL inheritance and propagationIn the Security tab of the installation folder, click Advanced. Check if "Replace all child object permission entries with inheritable permission entries from this object" is enabled, and review the effective permissions for subfolders. Verify that overly permissive entries (such as Everyone with Full Control) are propagating to child objects.Affected if Weak permissions on the parent folder are inherited by executables and DLLs within subfolders.
A user is affected if McKesson Cardiology (versions 11.0, 12.0-12.2, 13.0, 14.0, or 14.1.0) is installed and the installation directory or its executables/DLLs grant Write or Modify permissions to non-administrator accounts.
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.
From vendor dataRemediate by reviewing and hardening file permissions on the McKesson Cardiology installation directory according to least-privilege principles, restricting write and execute permissions to only authorized administrators and service accounts, then verify clinical functionality is unaffected.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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 $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18630 — 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-2018-18630 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