# CVE-2017-2140: Code injection in Tablacus Explorer

> Attackers can execute arbitrary scripts in the context of Tablacus Explorer by using a specially crafted directory.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 28 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7675-9w76-j5q2

## What is CVE-2017-2140?

CVE-2017-2140 is a high-severity code injection vulnerability in Gaku Tablacus Explorer, published on 28 Apr 2017. 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

Tablacus Explorer 17.3.30 and earlier allows arbitrary scripts to be executed in the context of the application due to specially crafted directory.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Gaku Tablacus Explorer.

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

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

## Is CVE-2017-2140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2140 is a high-severity code injection vulnerability in Gaku Tablacus Explorer, published on 28 Apr 2017. 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-2017-2140 in the wild and no public exploit code.

Affected product: Gaku Tablacus Explorer. 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-2140/ (Markdown: https://insights.sbomify.com/CVE-2017-2140/index.md)
```

## Sources

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

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