CVE-2022-41097
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 · uneditedNetwork Policy Server (NPS) RADIUS Protocol Information Disclosure 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 confidenceA vulnerability in Microsoft's Network Policy Server (NPS) allows an attacker to obtain sensitive information through the RADIUS protocol. This information disclosure could include authentication credentials, configuration details, or session data transmitted during RADIUS authentication and authorization processes.
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 dataall versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809all versions= 22h2all versionsall versionsall versionsall versions= r2all versions= r2all versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify if Network Policy Server (NPS) is installedRun 'Get-WindowsFeature -Name NPS' in PowerShell (Windows Server) or check 'Programs and Features > Windows Features' on client Windows. NPS appears under 'Network Policy and Access Services'.Affected if NPS is installed as a Windows feature or role
-
Confirm if NPS service is runningRun 'Get-Service -Name IAS' or 'Get-Service -Name "Network Policy Server"' in PowerShell. The service name is 'IAS' (Internet Authentication Service).Affected if The IAS/NPS service exists and is running
-
Check Windows version against affected listRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number.Affected if The system runs Windows 10 (any version), Windows 11 (any version), Windows 7, Windows 8.1, Windows Rt 8.1, Windows Server 2008/2012/2016 (any version)
-
Verify RADIUS is configured in NPSOpen NPS console (nps.msc) and check under 'RADIUS Clients and Servers'. Alternatively, run 'netsh nap client show configuration' to see if RADIUS authentication is enabled.Affected if RADIUS clients or remote access logging is configured in NPS, indicating active RADIUS processing
The system is affected if NPS is installed and running on a vulnerable Windows version (any of the listed Windows 10, 11, 7, 8.1, Server 2008/2012/2016 versions) with RADIUS configured.
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.
From vendor dataApply the Microsoft security update for CVE-2022-41097 to affected NPS servers. Until patched, restrict RADIUS traffic to trusted network sources using firewalls or network access control and monitor for anomalous RADIUS traffic patterns.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41097 — 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-2022-41097 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