dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-34728

MEDIUM · 5.5 CVSS v3.1 Developing Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
Windows Graphics Component 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 · low confidence

This is an information disclosure vulnerability in the Windows Graphics Component that allows a local attacker to potentially read sensitive information from memory due to improper handling of graphics operations. The vulnerability requires local access and has a partial confidentiality impact with no integrity or availability effects.

MitigationApply the relevant Microsoft security updates for Windows systems as they become available through standard patch management 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 data
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating 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
None
Availability
None

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from the Run dialog or execute 'systeminfo' in Command Prompt. Record the OS name, version, and build number shown.
    Affected if The detected Windows version matches any of the following: Windows 10 (any version including 20h2, 21h1, 21h2, 1607, 1809), Windows 11 (any version), Windows 7 (any version), Windows 8.1 (any version), Windows Rt 8.1 (any version), Windows Server 2008 (any version including R2), Windows Server 2012
  2. Verify Windows Graphics Component is in use
    Confirm the system has a graphics subsystem by checking that display drivers are loaded. In PowerShell, run 'Get-WmiObject Win32_VideoController' to list video controllers. Alternatively, verify the system has a desktop environment.
    Affected if The Windows Graphics Component is present and operational, which is true for virtually all Windows desktop and server installations with display capabilities.
  3. Check installed security updates for CVE-2022-34728
    Open Command Prompt or PowerShell and run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' to list installed updates. Look for a security update installed around September 2022 or later that corresponds to CVE-2022-34728. The update is typically listed as a Security Update for Windows.
    Affected if No security update addressing CVE-2022-34728 is installed, or the installed updates predate the September 2022 security patch release for this vulnerability.

A system is affected if it runs any of the listed Windows versions and is missing the relevant security update for CVE-2022-34728 from September 2022 or later.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Microsoft security updates for Windows systems as they become available through standard patch management processes.

Recommended fix High confidence
  1. Open Windows Update settings on the affected system
  2. Check for and install the latest Windows security updates
  3. Specifically look for the security update addressing CVE-2022-34728 (Windows Graphics Component Information Disclosure Vulnerability)
  4. Restart the system after applying the update
  5. Verify the update was successfully installed by checking Windows Update history

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34728 — 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-2022-34728 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