Windows 10 1809Operating system · Microsoft

CVE-2023-33155

HIGH · 7.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 10.0.17763.4645 / 10.0.19041.3208 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 Cloud Files Mini Filter 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
How this class of weakness works · CWE-284

The application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.

General guidance for the improper access control class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.4645
Windows 10 21h2Operating system
Affected:< 10.0.19041.3208
Windows 10 22h2Operating system
Affected:< 10.0.19045.3208
Windows 11 21h2Operating system
Affected:< 10.0.22000.2176
Windows 11 22h2Operating system
Affected:< 10.0.22621.1992
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating system
Affected:all versions

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.4645 / 10.0.19041.3208 / 10.0.19045.3208 or later
Fixed in 10.0.17763.464510.0.19041.320810.0.19045.3208
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1809: build 10.0.17763.4645 | Windows 10 21h2: build 10.0.19041.3208 | Windows 10 22h2: build 10.0.19045.3208 | Windows 11 21h2: build 10.0.22000.2176 | Windows 11 22h2: build 10.0.22621.1992 | Windows Server 2019/2022: apply latest cumulative security update containing the CVE-2023-33155

  1. Navigate to the Microsoft Update Guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-33155 to obtain the specific KB article number for your Windows version
  2. Open Windows Settings on the affected system
  3. Navigate to Windows Update > Check for updates
  4. Install the available security update for CVE-2023-33155
  5. Restart the system when prompted to complete the installation
  6. Verify the update was installed by checking Windows Update history or running 'winver' to confirm the build number matches the fixed version for your Windows release
Caveat Standard Windows cumulative update apply; no expected breaking changes for this security-only patch

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33155 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33155 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