# CVE-2018-18630: Misconfiguration in n/a

> Local attackers can execute arbitrary code due to insecure file permissions in the default installation of McKesson Cardiology software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j965-m9vq-3cg5

## What is CVE-2018-18630?

CVE-2018-18630 is a high-severity vulnerability in n/a, published on 6 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-18630?

It affects 3 products.


Products: Changehealthcare Cardiology Firmware, Mckesson Cardiology Firmware, Mckesson Horizon Cardiology Firmware.

## How do I fix CVE-2018-18630?

No fix has been published for CVE-2018-18630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-18630 being exploited?

There is no known exploitation of CVE-2018-18630 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18630 and fix it if it is affected.

What it is: CVE-2018-18630 is a high-severity vulnerability in n/a, published on 6 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18630 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-18630/ (Markdown: https://insights.sbomify.com/CVE-2018-18630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-18630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-18630
- OSV: https://osv.dev/vulnerability/CVE-2018-18630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-18630/
Summaries are generated and may contain mistakes; the official description above is the record.