Mobile Broadband Driver PackageApplication · Sierrawireless

CVE-2020-8948

HIGH · 7.8 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 5043 or later.
See remediation →
80/100
Remediation priority · High
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
The Sierra Wireless Windows Mobile Broadband Driver Packages (MBDP) before build 5043 allows an unprivileged user to overwrite arbitrary files in arbitrary folders using hard links. An unprivileged user could leverage this vulnerability to execute arbitrary code with system 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 confidence

The Sierra Wireless Windows Mobile Broadband Driver Packages (MBDP) before build 5043 contains a privilege escalation vulnerability where an unprivileged user can create hard links to overwrite arbitrary files in any folder on the system. This allows the attacker to gain SYSTEM-level code execution.

MitigationUpdate the Sierra Wireless MBDP driver packages to build 5043 or later. Apply the vendor patch to remediate the hard link vulnerability.

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
Mobile Broadband Driver PackageApplication
Affected:< 5043

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Check if Sierra Wireless MBDP software is installed
    Look for Sierra Wireless Mobile Broadband Driver Package in the list of installed programs via Control Panel > Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Sierra Wireless' or 'MBDP'.
    Affected if The software is not found in the installed programs list, meaning the driver package is not present on the system.
  2. Identify the installed build version
    Right-click the Sierra Wireless MBDP entry in Programs and Features and select Properties, or check the driver file version in Device Manager under Network adapters. Look for a build number or version field.
    Affected if The build number displayed is less than 5043, indicating the vulnerable version is installed.
  3. Verify the driver component is present
    Check for the presence of Sierra Wireless driver files in Program Files or Program Files (x86), typically under a Sierra Wireless directory. Also confirm the network adapter appears in Device Manager.
    Affected if The driver files or network adapter are present on the system, meaning the attack surface exists regardless of version display.
  4. Check driver version via Device Manager
    Open Device Manager, expand Network adapters, locate the Sierra Wireless Mobile Broadband device, right-click and select Properties, then view the Driver tab for version information.
    Affected if The driver version shown is below the fixed build 5043.

The system is affected if Sierra Wireless Mobile Broadband Driver Package is installed with a build number lower than 5043, as this version allows unprivileged hard link creation leading to SYSTEM code execution.

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 5043 or later
Fixed in 5043
Interim mitigation

Update the Sierra Wireless MBDP driver packages to build 5043 or later. Apply the vendor patch to remediate the hard link vulnerability.

Fix this in Mobile Broadband Driver Package Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-8948 — 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-2020-8948 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