CVE-2024-57972
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 · uneditedThe pairing API request handler in Microsoft HoloLens 1 (Windows Holographic) through 10.0.17763.3046 and HoloLens 2 (Windows Holographic) through 10.0.22621.1244 allows remote attackers to cause a Denial of Service (resource consumption and device unusability) by sending many requests through the Device Portal framework.
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 confidenceThe pairing API request handler in Microsoft HoloLens Device Portal lacks proper rate limiting, allowing remote attackers to send numerous requests that exhaust system resources and render the device unusable. This is a resource consumption DoS affecting both HoloLens 1 and 2 versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm HoloLens device presence on networkIdentify HoloLens devices on your network by scanning for devices responding to port 80/443 or by checking your network inventory/MDM for HoloLens 1 or HoloLens 2 devices.Affected if Any HoloLens 1 or 2 device exists on the network with Device Portal accessible.
-
Verify Device Portal is enabledCheck if the HoloLens Device Portal web interface is accessible by navigating to https://<hololens-ip> in a browser or running 'curl -k https://<hololens-ip>' from a command line.Affected if The Device Portal returns an HTTP 200 response and displays the login page.
-
Confirm pairing API endpoint accessibilityCheck if the pairing API is reachable by attempting a request to the endpoint (typically /api/holographic/management/pairing or similar pairing-related paths under /api/). Use: curl -k -X POST https://<hololens-ip>/api/holographic/management/pairingAffected if The endpoint responds without authentication or returns a pairing-related error indicating the API is exposed.
-
Check for rate limiting configurationReview the Device Portal configuration or check system event logs for any rate limiting or throttling indicators. Inspect any proxy/WAF configurations in front of the Device Portal for rate limit rules.Affected if No rate limiting rules are found on the Device Portal or upstream network devices, and the pairing API accepts requests without throttling.
-
Review authentication settingsExamine whether the pairing API requires authentication or can be accessed anonymously. Check the Device Portal security settings and API permissions.Affected if The pairing API is accessible without requiring authentication or can be accessed via the Device Portal without enforced rate limiting.
A user is affected if they have an exposed HoloLens Device Portal with the pairing API accessible without rate limiting controls, allowing unlimited requests to exhaust device resources.
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.
From vendor dataImplement rate limiting and request throttling on the Device Portal pairing API endpoint; apply Microsoft firmware updates when available. Consider network-level protections such as WAF or IP filtering to limit request rates.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57972 — 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-57972 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