Bluetooth StackApplication · Toshiba

CVE-2015-0884

MEDIUM · 6.9 CVSS v2.0 Published 2015-02-28
Fix available
A fix is available. Upgrade to after 2.2.13 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Unquoted Windows search path vulnerability in Toshiba Bluetooth Stack for Windows before 9.10.32(T) and Service Station before 2.2.14 allows local users to gain privileges via a Trojan horse application with a name composed of an initial substring of a path that contains a space character.

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 confidence

Local privilege escalation vulnerability in Toshiba Bluetooth Stack and Service Station for Windows due to an unquoted service path containing spaces. When the service executable launches, Windows attempts to find and execute the first executable matching the path substring before the first space, allowing an attacker to place a malicious executable with a name like 'Program.exe' to achieve code execution with elevated privileges.

MitigationUpdate Toshiba Bluetooth Stack to version 9.10.32(T) or later and Service Station to version 2.2.14 or later to obtain patched binaries with properly quoted service paths.

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
Bluetooth StackApplication
Affected:= 9.10.27\(t\)
Service StationApplication
Affected:<= 2.2.13

CVSS 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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Toshiba Bluetooth Stack version
    Open Registry Editor and navigate to HKLM\SOFTWARE\Toshiba\BluetoothStack\Version, or check the file version of C:\Program Files\Toshiba\Bluetooth Stack\ToshibaBluetoothStack.exe
    Affected if Version equals 9.10.27(t)
  2. Check Toshiba Service Station version
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Service Station or check the file version of C:\Program Files\Toshiba\Service Station\ServiceStation.exe
    Affected if Version is 2.2.13 or lower
  3. Identify Toshiba Bluetooth Stack service
    Open Command Prompt and run: sc query type= service to list services, then find the Toshiba Bluetooth service name (typically 'Toshiba Bluetooth Stack' or similar), then run: sc qc "<service_name>" to view the binary path
    Affected if The BINPATH displayed contains spaces and is not enclosed in quotation marks
  4. Identify Toshiba Service Station service
    Run: sc query type= service to find the Service Station service, then run: sc qc "<service_name>" to view the binary path
    Affected if The BINPATH displayed contains spaces and is not enclosed in quotation marks
  5. Verify unquoted path exploitation scenario
    If an unquoted path contains spaces such as C:\Program Files\Toshiba\Bluetooth Stack\TOSDKBTV.exe, check if a malicious executable could be placed at an earlier path component like C:\Program.exe
    Affected if The service path has unquoted spaces and a writable location exists earlier in the path where an attacker could place a malicious executable

You are affected if either Toshiba Bluetooth Stack version 9.10.27(t) or Toshiba Service Station version 2.2.13 or lower is installed AND the corresponding service binary path contains unquoted spaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.2.13
Interim mitigation

Update Toshiba Bluetooth Stack to version 9.10.32(T) or later and Service Station to version 2.2.14 or later to obtain patched binaries with properly quoted service paths.

Fix this in Bluetooth Stack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0884 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0884 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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