CVE-2024-49094
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 · uneditedWireless 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 confidenceCVE-2024-49094 is an Elevation of Privilege vulnerability in the Windows Wireless Wide Area Network Service (WwanSvc), a component responsible for managing mobile broadband connections on Windows systems. The vulnerability allows an authenticated attacker to gain elevated privileges by exploiting improper handling within this service.
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< 10.0.17763.6659< 10.0.19044.5247< 10.0.19045.5247< 10.0.22621.4602< 10.0.22631.4602< 10.0.26100.2605< 10.0.17763.6659< 10.0.25398.1308CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' in cmd to get the build number.Affected if The installed version is less than the affected build numbers: 17763.6659 (Win10 1809/Server 2019), 19044.5247 (Win10 21h2), 19045.5247 (Win10 22h2), 22621.4602 (Win11 22h2), 22631.4602 (Win11 23h2), 26100.2605 (Win11 24h2), 25398.1308 (Server 2022 23h2)
-
Verify WwanSvc service statusOpen Services (services.msc) or run 'Get-Service WwanSvc' in PowerShell. Check if the service exists and its current status (Running/Stopped).Affected if The WwanSvc service is present and set to Running or Automatic start; the vulnerability only applies when this service is enabled
-
Confirm patch installation statusRun 'Get-HotFix | Where-Object {$_.HotFixID -like "KB*"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recently installed updates. Check for November 2024 or later Windows security updates.Affected if No recent security updates from November 2024 or later are installed, indicating the system may be unpatched
The system is affected if it runs a vulnerable Windows version listed above AND has the WwanSvc service enabled, and lacks the November 2024 security updates that address this vulnerability.
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.
dbcve · scoped10.0.17763.665910.0.19044.524710.0.19045.5247
Apply the latest Windows security updates to patch this vulnerability in affected Windows systems running WwanSvc; verify through system inventory that all applicable patches have been deployed.
November 2024 Windows Security Update (KB5044284 or version-specific equivalent) - install the appropriate KB for your Windows version from https://catalog.update.microsoft.com
- Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
- Determine the appropriate KB patch for your Windows version from the November 2024 security updates (CVE-2024-49094)
- Open Windows Update (Settings > Update & Security > Windows Update)
- Click 'Check for updates' to download and install the relevant security update
- Restart the system when prompted to complete the installation
- Verify the installation by checking the installed updates list for the November 2024 security update containing CVE-49094
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49094 — 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-2024-49094 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