# CVE-2018-1437: Other in Notes

> A local attacker can execute arbitrary code or cause a crash in IBM Notes via DLL hijacking due to untrusted search paths.

- **Severity:** High 7.8 (`CVSS:3.0/A:H/AC:L/AV:L/C:H/I:H/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x3h5-3jh8-247m

## What is CVE-2018-1437?

CVE-2018-1437 is a high-severity vulnerability in IBM Notes, published on 14 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

IBM Notes 8.5 and 9.0 could allow an attacker to execute arbitrary code on the system, caused by an error related to multiple untrusted search path. A local attacker could exploit this vulnerability to DLL hijacking to execute arbitrary code on the system or cause the application to crash. IBM X-Force ID: 139565.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Ibm Notes.

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

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

## Is CVE-2018-1437 being exploited?

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

## Other vulnerabilities in IBM Notes

- [CVE-2018-1435](https://insights.sbomify.com/CVE-2018-1435/): Other in Notes (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1437 is a high-severity vulnerability in IBM Notes, published on 14 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1437 in the wild and no public exploit code.

Affected product: IBM Notes. 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-1437/ (Markdown: https://insights.sbomify.com/CVE-2018-1437/index.md)
```

## Sources

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

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