# CVE-2017-2214: Path traversal in AppCheck

> Attackers can execute arbitrary code by placing a malicious executable in a directory searched by AppCheck, requiring users to upgrade to a patched version.

- **Severity:** High 8.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-48jc-r7pp-3grh

## What is CVE-2017-2214?

CVE-2017-2214 is a high-severity path traversal vulnerability in JIRANSOFT JAPAN, INC. AppCheck, published on 9 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in AppCheck and AppCheck Pro prior to version 2.0.1.15 allows an attacker to execute arbitrary code via a specially crafted executable file in an unspecified directory.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2017-2214?

It affects 2 products.


Products: Jiransoft Appcheck, Jiransoft Appcheck Pro.

## How do I fix CVE-2017-2214?

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

## Is CVE-2017-2214 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2214 and fix it if it is affected.

What it is: CVE-2017-2214 is a high-severity path traversal vulnerability in JIRANSOFT JAPAN, INC. AppCheck, published on 9 Jun 2017. 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-2017-2214 in the wild and no public exploit code.

Affected product: JIRANSOFT JAPAN, INC. AppCheck. 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-2017-2214/ (Markdown: https://insights.sbomify.com/CVE-2017-2214/index.md)
```

## Sources

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

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