CVE-2017-2149
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUntrusted 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a DLL hijacking vulnerability in installer software for Toshiba memory cards with NFC, wireless LAN (FlashAir), and TransferJet functionality. The installers use an untrusted search path, allowing remote attackers to place a malicious DLL in an unspecified directory that gets loaded with elevated privileges during installation, enabling privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.00.03<= 1.00.04<= 1.00.06<= 1.02<= 2.00.03<= 3.00.01<= 3.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Toshiba FlashAir softwareCheck Program Files, Program Files (x86), and Add/Remove Programs for Toshiba FlashAir entries. Also check for any Toshiba or Sandisk memory card utility software that handles FlashAir functionality.Affected if Toshiba FlashAir installer or related utility software is found with version <= 1.00.03, <= 1.00.04, <= 1.00.06, <= 2.00.03, <= 3.00.01, or <= 3.0.2
-
Locate FlashAir installer executable and verify versionFind the installer executable file on the system or in download folders. Right-click to view Properties and check the Details tab for version information, or run the installer with version check flags if available.Affected if The installer version matches any of the vulnerable version ranges listed in the affected products
-
Inspect installer directory for unexpected DLLsOpen the directory containing the FlashAir installer executable. Examine all DLL files present in that folder. Look for DLLs that are not part of the official installer package.Affected if Unexpected or unauthorized DLL files exist in the same directory as the installer executable
-
Check for DLL search path vulnerability in installerUse Process Monitor or similar tool to trace DLL loading when running the installer. Observe whether the installer loads DLLs from the current working directory before checking system directories.Affected if The installer loads DLLs from its own directory without validation, enabling hijacking
-
Review recent installation activity logsCheck Windows Event Viewer under Windows Logs > Application for recent entries related to Toshiba FlashAir or memory card installer installations.Affected if Recent installation events show the vulnerable installer was run on the system
A user is affected if Toshiba FlashAir installer software with a version matching the affected ranges is present on the system and the installer directory contains unexpected DLL files or exhibits untrusted search path behavior.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataObtain and deploy updated installer versions from the vendor (Toshiba/Sandisk) that fix the untrusted search path issue. Verify that installer directories do not contain unauthorized DLLs before running installations.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-2149 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data