dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-49109

MEDIUM · 6.6 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 →
68/100
Remediation priority · Elevated
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
Wireless Wide Area Network Service (WwanSvc) 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 Wireless Wide Area Network Service (WwanSvc), which manages mobile broadband and cellular connectivity. The vulnerability allows an authenticated attacker to gain elevated privileges, likely by exploiting improper access controls or input validation within the service.

MitigationApply the Microsoft security update for CVE-2024-49109 through standard Windows Update or patch management systems. Prioritize systems with mobile broadband capability.

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

CVSS:3.1/AV:P/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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact build number
    Affected if The build number falls below any of these thresholds: 17763.6659 (Win10 1809/Server2019), 19044.5247 (Win10 21h2), 19045.5247 (Win10 22h2), 22621.4602 (Win11 22h2), 22631.4602 (Win11 23h2), 26100.2605 (Win11 24h2), or 25398.1308 (Server2022 23h2)
  2. Verify WwanSvc service presence
    Run 'sc query WwanSvc' in Command Prompt or 'Get-Service -Name WwanSvc' in PowerShell to check if the Wireless Wide Area Network Service exists on the system
    Affected if The service exists and is running on the system, indicating the vulnerable component is present
  3. Confirm mobile broadband capability
    Check Device Manager for mobile broadband adapters (look under Network Adapters for terms like mobile broadband, cellular, WWAN, LTE, or 5G), or run 'netsh mbn show readiness' to see cellular readiness status
    Affected if The system has mobile broadband hardware or cellular capability enabled, making it a likely target for exploitation
  4. Check for security update installation
    Run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' in PowerShell to list installed updates, then search for any updates from December 2024 or later that correspond to CVE-2024-49109
    Affected if No December 2024 or later security update for CVE-2024-49109 is installed

The system is likely affected if it runs a vulnerable Windows version (as listed in the affected versions) AND has the WwanSvc service present AND lacks the December 2024 security update.

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-49109 through standard Windows Update or patch management systems. Prioritize systems with mobile broadband capability.

Recommended fix High confidence

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.4602 | Windows 11 24h2: 10.0.26100.2605 | Windows Server 2019: 10.0.17763.6659 | Windows Server 2022 23h2: 10.0.25398.1308

  1. Obtain the security update from Microsoft Update Catalog or Windows Update for this CVE (referenced in Microsoft Security Response Center)
  2. Install the appropriate KB update for your Windows version: KB5055527 (January 2025) or subsequent relevant patch
  3. Restart the affected system to complete the patch installation
  4. Verify the update was installed successfully by checking Windows Update history or using 'winver' command to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows patching applies; test in staging environment before broad deployment to ensure compatibility with existing applications

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
  • 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-2024-49109 — 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-49109 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