# CVE-2017-2149: Other in Installer for SDHC Memory Card with embedded TransferJetTM functionality Configuration Software

> Attackers can execute arbitrary code and gain privileges via a Trojan horse DLL due to an untrusted search path in Toshiba memory card software installers.

- **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-pvr8-f2qg-6jxg

## What is CVE-2017-2149?

CVE-2017-2149 is a high-severity vulnerability in Toshiba Corporation Installer for SDHC Memory Card with embedded TransferJetTM functionality Configuration Software, 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

Untrusted search path vulnerability in installers of the software for SDHC/SDXC Memory Card with embedded NFC functionality Software Update Tool V1.00.03 and earlier, SDHC Memory Card with embedded wireless LAN functionality FlashAir Configuration Software V3.0.2 and earlier, SDHC Memory Card with embedded wireless LAN functionality FlashAir Software Update tool (SD-WE series<W-03>) V3.00.01, SDHC Memory Card with embedded wireless LAN functionality FlashAir Software Update tool (SD-WD/WC series<W-02>) V2.00.03 and earlier, SDHC Memory Card with embedded wireless LAN functionality FlashAir Software Update tool (SD-WB/WL series) V1.00.04 and earlier, SDHC Memory Card with embedded TransferJet functionality Configuration Software V1.02 and earlier, SDHC Memory Card with embedded TransferJet functionality Software Update tool V1.00.06 and earlier allows remote attackers to gain privileges via a Trojan horse DLL in an unspecified directory.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Toshiba Flashair.

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

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

## Is CVE-2017-2149 being exploited?

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

## Other vulnerabilities in Toshiba Corporation Installer for SDHC Memory Card with embedded TransferJetTM functionality Configuration Software

- [CVE-2016-4863](https://insights.sbomify.com/CVE-2016-4863/): Auth bypass in FlashAir Class 6 model (medium 4.3)
- [CVE-2017-2162](https://insights.sbomify.com/CVE-2017-2162/): Hardcoded credentials in FlashAirTM SDHC Memory Card (SD-WD/WC Series <W-02>) (medium 4.3)
- [CVE-2017-2161](https://insights.sbomify.com/CVE-2017-2161/): Missing authorization in FlashAirTM SDHC Memory Card (SD-WD/WC Series <W-02>) (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2149 is a high-severity vulnerability in Toshiba Corporation Installer for SDHC Memory Card with embedded TransferJetTM functionality Configuration Software, 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-2149 in the wild and no public exploit code.

Affected product: Toshiba Corporation Installer for SDHC Memory Card with embedded TransferJetTM functionality Configuration Software. 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-2149/ (Markdown: https://insights.sbomify.com/CVE-2017-2149/index.md)
```

## Sources

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

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