CVE-2017-9247
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 · uneditedMultiple unquoted service path vulnerabilities in Sierra Wireless Windows Mobile Broadband Driver Package (MBDP) with build ID < 4657 allows local users to launch processes with elevated privileges.
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 confidenceMultiple unquoted service path vulnerabilities exist in Sierra Wireless Windows Mobile Broadband Driver Package (MBDP) builds prior to 4657. When Windows service executable paths contain spaces and are not enclosed in quotation marks, local attackers can place malicious executables in intermediate path directories to achieve privilege escalation from user-level to SYSTEM privileges.
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 dataall versionsall versionsall versionsCVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 Sierra Wireless servicesRun 'sc queryex type= service state= all' and look for services containing 'Sierra Wireless', 'Sierra', 'Em7345', 'Em7455', or 'Location Sensor' in the SERVICE_NAME or DISPLAY_NAME fieldsAffected if Any service with Sierra Wireless in the name is found on the system
-
Inspect the executable path for each Sierra Wireless serviceFor each identified service, run 'sc qc <service_name>' and examine the BINARY_PATH_NAME field. Check if the path contains spaces and is not enclosed in quotation marksAffected if The BINARY_PATH_NAME contains spaces but does not start and end with double quotes (e.g., C:\Program Files\Sierra\driver.exe instead of "C:\Program Files\Sierra\driver.exe")
-
Cross-check with Windows RegistryOpen Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Services\, locate Sierra Wireless service entries, and verify the ImagePath value under each service keyAffected if The ImagePath value shows an unquoted path with spaces (e.g., C:\Program Files\Sierra Wireless\Driver\somefile.exe)
-
Confirm driver version if possibleCheck the driver's file version by right-clicking the executable in the binPath, selecting Properties, and viewing the Details tab. Compare the build version to 4657Affected if The driver build version is earlier than 4657 or cannot be determined (all versions prior to patch are affected)
The environment is affected if any Sierra Wireless service (Em7345, Em7455, or Location Sensor Driver) has an unquoted executable path containing spaces, which could allow privilege escalation to SYSTEM level.
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 dataUpdate Sierra Wireless MBDP to build 4657 or later, which contains the vendor patch for the unquoted service path vulnerability. Alternatively, manually review and quote all service executable paths associated with the driver.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9247 — 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-9247 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