dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-49077

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 a local Elevation of Privilege (EoP) vulnerability in the Windows Mobile Broadband Driver, which runs in kernel mode. A local authenticated attacker could exploit this to gain higher privileges on the affected system, potentially achieving SYSTEM-level access.

MitigationApply the Microsoft security update for CVE-2024-49077 through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems with local user access.

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 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
Windows Server 2025Operating system
Affected:< 10.0.26100.2605

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. Check Windows build version
    Run 'winver' from command prompt or check 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact build number
    Affected if The build number is lower than the version specified for your Windows edition in the CVE affected products list (e.g., below 10.0.17763.6659 for Windows 10 1809/Server 2019)
  2. Identify Windows edition
    Run 'winver' or check System Properties to determine if you are on Windows 10 1809, 21h2, 22h2, Windows 11 23h2/24h2, or Windows Server 2019/2022/2025
    Affected if The edition matches one listed in the affected products with a build number below the specified threshold
  3. Verify Mobile Broadband driver presence
    Open Device Manager, expand 'Network adapters' and look for any Mobile Broadband or WWAN-related adapters (such as 'Mobile Broadband Device' or WWAN adapters from mobile operators). Alternatively, run 'driverquery /v | findstr -i "mobile\|wwan"'
    Affected if A Mobile Broadband or WWAN network adapter driver is installed on the system
  4. Check driver file version (optional)
    If a Mobile Broadband driver is found, right-click the device in Device Manager, go to Driver tab, and note the Driver Version/Date. For technical users, the driver files are typically located in C:\Windows\System32\drivers\ and may include wwanserv.exe or WWAN-related driver files
    Affected if The driver version is outdated or matches a version predating the November 2024 security update

You are likely affected if your Windows build number falls within the affected ranges AND a Mobile Broadband/WWAN driver is present on the 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 Microsoft security update for CVE-2024-49077 through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems with local user access.

Recommended fix High confidence

Apply November 2024 Windows Security Update (or later) - specific KB number available at msrc.microsoft.com

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Ensure the update includes the KB for CVE-2024-49077 (refer to Microsoft Security Update Guide for the specific KB number)
  4. Restart the system after the update is installed
  5. Verify the installed version matches or exceeds the fixed build number for your Windows version (e.g., 10.0.17763.6659 for Windows 10 1809/Server 2019)

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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