dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-49078

MEDIUM · 6.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.17763.6659 / 10.0.19044.5247 or later.
See remediation →
73/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
Windows Mobile Broadband Driver Elevation of Privilege Vulnerability

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 · moderate confidence

This is an Elevation of Privilege vulnerability in the Windows Mobile Broadband Driver. The vulnerability allows an attacker to elevate their privileges on the affected system through the Mobile Broadband driver component.

MitigationApply the security update(s) addressed in the Microsoft security bulletin when available. Until patches are applied, restrict access to untrusted networks and monitor for suspicious driver activity.

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
Windows 10 1809Operating system
Affected:< 10.0.17763.6659
Windows 10 21h2Operating system
Affected:< 10.0.19044.5247
Windows 10 22h2Operating system
Affected:< 10.0.19045.5247
Windows 11 22h2Operating system
Affected:< 10.0.22621.4602
Windows 11 23h2Operating system
Affected:< 10.0.22631.4602
Windows 11 24h2Operating system
Affected:< 10.0.26100.2605
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1308

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

CVSS:3.1/AV:P/AC:L/PR:N/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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine your Windows build number
    Affected if The build number falls below any of these thresholds: 17763.6659, 19044.5247, 19045.5247, 22621.4602, 22631.4602, 26100.2605, 25398.1308
  2. Locate Mobile Broadband driver
    Open Device Manager, expand 'Network adapters', and look for entries containing 'Mobile Broadband' or 'MW' or check via command: 'driverquery /v | findstr -i mobile'
    Affected if A Mobile Broadband driver is installed on the system
  3. Verify driver is loaded
    Run 'sc query mwrfl' or check 'driverquery' output for any loaded driver related to Mobile Broadband
    Affected if The Mobile Broadband driver is currently loaded or running as a service

You are affected if your Windows build is below the listed thresholds AND the Mobile Broadband driver is installed and loaded on your system.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.6659 / 10.0.19044.5247 / 10.0.19045.5247 or later
Fixed in 10.0.17763.665910.0.19044.524710.0.19045.5247
Interim mitigation

Apply the security update(s) addressed in the Microsoft security bulletin when available. Until patches are applied, restrict access to untrusted networks and monitor for suspicious driver activity.

Recommended fix High confidence

Apply the November 2024 security update (KB5046732 or subsequent updates) for your specific Windows version - the fixed builds are: Windows 10 1809 (10.0.17763.6659), Windows 10 21h2 (10.0.19044.5247), Windows 10 22h2 (10.0.19045.5247), Windows 11 22h2 (10.0.22621.4602), Windows 11 23h2 (10.0.22631.

  1. Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2024-49078
  3. Download the appropriate security update for your Windows version from the Microsoft Update Catalog
  4. Install the security update via Windows Update (Settings > Update & Security > Windows Update > Check for updates) or by manually installing the downloaded .msu file
  5. Restart the computer to complete the update installation
  6. Verify the update was installed successfully by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows security update - minimal risk of breaking changes; however, test in non-production environment if concerned about compatibility with custom Mobile Broadband configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-49078 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