# CVE-2019-8463: Path traversal in Check Point Endpoint Security Client for Windows

> An attacker can cause a denial of service by writing service log files to non-standard locations in Check Point Endpoint Security Client.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3jx2-x7xj-8x2c

## What is CVE-2019-8463?

CVE-2019-8463 is a high-severity path traversal vulnerability in Check Point Endpoint Security Client for Windows, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial of service vulnerability was reported in Check Point Endpoint Security Client for Windows before E82.10, that could allow service log file to be written to non-standard locations.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2019-8463?

It affects 1 product.


Products: Checkpoint Endpoint Security Clients.

## How do I fix CVE-2019-8463?

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

## Is CVE-2019-8463 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8463 and fix it if it is affected.

What it is: CVE-2019-8463 is a high-severity path traversal vulnerability in Check Point Endpoint Security Client for Windows, published on 23 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8463 in the wild and no public exploit code.

Affected product: Check Point Endpoint Security Client for Windows. 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-2019-8463/ (Markdown: https://insights.sbomify.com/CVE-2019-8463/index.md)
```

## Sources

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

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