# CVE-2018-15670: Other in n/a

> An attacker can trigger arbitrary URL handling in Airmail for macOS by abusing HTML event handlers during email navigation, potentially leading to code execution.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cqgx-5gh9-5jwx

## What is CVE-2018-15670?

CVE-2018-15670 is a medium-severity vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. Its primary WebView instance implements "webView:decidePolicyForNavigationAction:request:frame:decisionListener:" such that OpenURL is the default URL handler. A navigation request is processed by the default URL handler only if the currentEvent is NX_LMOUSEUP or NX_OMOUSEUP. An attacker may abuse HTML elements with an EventHandler for a chance to validate navigation requests for URLs that are processed during the NX_LMOUSEUP event triggered by clicking an email.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Bloop Airmail.

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

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

## Is CVE-2018-15670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15670 is a medium-severity vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-15670 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-15670/ (Markdown: https://insights.sbomify.com/CVE-2018-15670/index.md)
```

## Sources

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

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