CVE-2022-37958
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 · uneditedSPNEGO Extended Negotiation (NEGOEX) Security Mechanism Remote Code Execution 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 remote code execution vulnerability exists in the SPNEGO (Simple and Protected GSS-API Negotiation Mechanism) Extended Negotiation (NEGOEX) security mechanism. The vulnerability allows an attacker to execute arbitrary code on affected systems via the NEGOEX protocol handler.
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= 1607= 1809all versionsall versionsall versions= r2all versions= r2all versionsall 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows versionRun 'winver' from Start menu search, or execute 'systeminfo' in Command Prompt and look for OS Name and OS VersionAffected if The displayed Windows version matches any of the affected versions listed (Windows 10 versions 20h2/21h1/21h2/1607/1809, Windows 11, Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012/2012 R2, Windows Server 2016, Windows Server 2019)
-
Confirm NEGOEX protocol component presenceCheck for the presence of spnego.dll or negoexts.dll in System32 directory by running 'dir %WINDIR%\System32\spnego.dll' and 'dir %WINDIR%\System32\negoexts.dll'Affected if The DLL files exist on the system, indicating the NEGOEX/SPNEGO component is present (this applies to all affected Windows versions)
-
Check SPNEGO authentication usageReview Windows Authentication events in Event Viewer under Security logs, or check network captures for SPNEGO/Kerberos negotiation traffic on ports 88, 445, or 139Affected if The system is used for domain authentication, Kerberos, or NTLM authentication - which enables the NEGOEX protocol handler to process incoming negotiation requests
If the system runs any affected Windows version listed in the CVE and uses Windows authentication (Kerberos/SPNEGO), it is likely vulnerable and should be checked against Microsoft security bulletins for patch status.
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 · scopedApply the relevant Microsoft security patches for CVE-2022-37958. Prioritize patching affected Windows server and client systems, particularly those handling authentication traffic.
Install the Microsoft security update for CVE-2022-37958 (released September 2022)
- Check for and install the latest Windows security updates from Microsoft Update or your organization's patch management system
- Ensure automatic updates are enabled for Windows Update
- After patching, verify the NEGOEX security mechanism is updated by checking the installed security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37958 — 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-37958 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