dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-28902

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 or later.
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 Remote Access Connection Manager 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 confidence

This is an information disclosure vulnerability in Windows Remote Access Connection Manager (rascman.exe). The vulnerability allows a local attacker to potentially access sensitive information that should not be otherwise accessible. The CVSS 5.5 score indicates moderate severity with low attack complexity and no privileges required.

MitigationApply the Microsoft security update for CVE-2024-28902 through standard Windows Update or manual patch deployment. Verify Remote Access connectivity functionality after patching.

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 10 1507Operating system
Affected:< 10.0.10240.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

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. Determine your Windows version
    Run 'winver' from the command prompt or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for the 'CurrentBuild' and 'DisplayVersion' values
    Affected if The Windows version matches any of the affected builds: Windows 10 1507 (<10.0.10240.20651), 1607 (<10.0.14393.6981), 1809 (<10.0.17763.5820), 21h2 (<10.0.19044.4412), 22h2 (<10.0.19045.4412), or Windows 11 21h2 (<10.0.22000.2899), 22h2 (<10.0.22621.3593), 23h2 (<10.0.22631.3593)
  2. Locate the rascman.exe file
    Verify that C:\Windows\System32\rascman.exe exists on the system using 'dir C:\Windows\System32\rascman.exe' or 'Get-Item C:\Windows\System32\rascman.exe'
    Affected if The file exists on the system (the vulnerable component is present)
  3. Check rascman.exe file version
    Right-click rascman.exe in System32, go to Details tab, or run 'wmic datafile where name="C:\Windows\System32\rascman.exe" get Version,FileSize,LastModified'
    Affected if The file version is lower than the fixed version for your specific Windows build (compare against the version thresholds listed in the affected products)
  4. Verify Remote Access service presence
    Run 'sc query RemoteAccess' or check Services.msc for the 'Routing and Remote Access' service status
    Affected if The Remote Access service is installed on the system (the vulnerable code path can be triggered)
  5. Confirm patch installation status
    Run 'wmic qfe list' or check Windows Update history for security updates installed after the CVE-2024-28902 patch date (released June 2024)
    Affected if No security update for CVE-2024-28902 has been installed, or the installed updates do not include the fix for this vulnerability

You are affected if your Windows version falls within any of the affected build ranges AND the rascman.exe file exists on your system AND the June 2024 security update for CVE-2024-28902 has not been installed.

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
Upgrade available Upgrade to 10.0.10240.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply the Microsoft security update for CVE-2024-28902 through standard Windows Update or manual patch deployment. Verify Remote Access connectivity functionality after patching.

Recommended fix High confidence

June 2024 Windows Security Update (KB5039212 or subsequent updates) - specific build numbers vary by Windows version as listed in the affected versions

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download and install the June 2024 security update (or later) from the Microsoft Update Catalog for your specific Windows version
  4. Verify the update installed successfully by checking the installed updates in Control Panel > Programs and Features > View installed updates
  5. Confirm the version matches or exceeds the fixed build for your Windows release (e.g., Windows 10 22h2 should be >= 10.0.19045.4412)
Caveat Standard Windows security update with no expected breaking changes; as with any system update, ensure critical business applications are tested in a staging environment first

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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