CVE-2024-28900
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 · uneditedWindows 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 confidenceThis is an information disclosure vulnerability in Windows Remote Access Connection Manager (rasman.dll). The vulnerability allows a local authenticated attacker to potentially access sensitive information that should be protected. The flaw exists in how the Remote Access Connection Manager handles certain operations or data, leading to unintended information exposure.
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< 10.0.10240.20651< 10.0.14393.6981< 10.0.17763.5820< 10.0.19044.4412< 10.0.19045.4412< 10.0.22000.2899< 10.0.22621.3593< 10.0.22631.3593CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows version and build numberOpen Settings > System > About, or run 'winver' command, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command PromptAffected if The Windows version and build number fall within any of the affected ranges listed (e.g., 10.0.10240.20651 or lower for 1507, 10.0.19045.4412 or lower for 10 22h2, etc.)
-
Locate the rasman.dll fileFind rasman.dll in the System32 folder, typically at C:\Windows\System32\rasman.dllAffected if The file exists on the system (it is a core Windows component)
-
Check rasman.dll file versionRight-click rasman.dll in File Explorer, go to Properties > Details, or run 'dir C:\Windows\System32\rasman.dll' and note the version timestamp, or use a PowerShell command like '[System.Diagnostics.FileVersionInfo]::GetVersionInfo("C:\Windows\System32\rasman.dll")'Affected if The file version is lower than the versions specified in the CVE for your Windows release (compare the Product Version or File Version field)
-
Verify if security update is installedOpen Settings > Windows Update > Update history, or run 'wmic qfe list' in Command Prompt to see installed hotfixes, looking for KB5034441 or subsequent relevant security patchesAffected if The specific security update for CVE-2024-28900 (KB5034441 or later) is NOT listed among installed updates
You are affected if your Windows version/build falls within the affected ranges AND the rasman.dll file version is below the patched threshold AND the corresponding security update is not installed.
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 · scoped10.0.10240.2065110.0.14393.698110.0.17763.5820
Apply the Microsoft security update (KB5034441 or subsequent relevant patches) to address this vulnerability. As a defense-in-depth measure, ensure proper least-privilege principles are followed and restrict local account privileges where possible.
Upgrade to the latest cumulative security update containing the fix: Windows 10 1507 to 10.0.10240.20651 | Windows 10 1607 to 10.0.14393.6981 | Windows 10 1809 to 10.0.17763.5820 | Windows 10 21h2 to 10.0.19044.4412 | Windows 10 22h2 to 10.0.19045.4412 | Windows 11 21h2 to 10.0.22000.2899 | Windows
- Open Windows Settings
- Navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Alternatively, manually download the specific security update for your Windows version from the Microsoft Update Catalog (search for CVE-2024-28900)
- Restart the system after updates are installed
- Verify the installed update by running 'winver' to confirm the version matches or exceeds the fixed version for your build
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28900 — 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-2024-28900 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