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

> A format string vulnerability in Pulse Secure Desktop for macOS allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c49m-xjh6-2h4v

## What is CVE-2018-15749?

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

### Official description

The Pulse Secure Desktop (macOS) 5.3RX before 5.3R5 and 9.0R1 has a Format String Vulnerability.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Pulsesecure Pulse Secure Desktop Client.

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

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

## Is CVE-2018-15749 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8239](https://insights.sbomify.com/CVE-2020-8239/): Privilege escalation in Pulse Secure Desktop Cient (critical 9.8)
- [CVE-2020-8254](https://insights.sbomify.com/CVE-2020-8254/): Path traversal in Pulse Secure Desktop Client (high 8.8)
- [CVE-2020-8240](https://insights.sbomify.com/CVE-2020-8240/): Privilege escalation in Pulse Secure Desktop Client (high 7.8)
- [CVE-2020-8248](https://insights.sbomify.com/CVE-2020-8248/): Privilege escalation in Pulse Secure Desktop Client (high 7.8)
- [CVE-2020-8249](https://insights.sbomify.com/CVE-2020-8249/): Memory corruption in Pulse Secure Desktop Client (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15749 is a medium-severity vulnerability in n/a, published on 6 Sep 2018. 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-15749 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-15749/ (Markdown: https://insights.sbomify.com/CVE-2018-15749/index.md)
```

## Sources

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

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