CVE-2021-47662
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 · uneditedDue to missing authorization an unauthenticated remote attacker can cause a DoS attack by connecting via HTTPS and triggering the shutdown button.
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 · high confidenceThis vulnerability exists in a web interface or API endpoint that exposes a shutdown function. The application fails to verify user authorization before executing shutdown commands, allowing any unauthenticated remote attacker who can reach the HTTPS endpoint to trigger a denial of service by activating the shutdown button.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify web-exposed administrative interfacesReview network exposure of your application. Check for publicly accessible HTTPS endpoints that serve administrative or management functions, including /admin, /management, /api/admin, or similar paths. Use network scans or review reverse proxy configurations.Affected if Any administrative web interface or API endpoint is accessible via HTTPS without VPN or network segmentation.
-
Locate shutdown or power-off endpointsSearch application source code, API documentation, or web interface routes for shutdown, poweroff, reboot, halt, stop, or similar termination functions. Check JavaScript files for button handlers triggering shutdown actions.Affected if The application contains a shutdown or system power-off function exposed via web API or UI button.
-
Verify authentication is enforced on shutdown endpointsInspect the code or configuration handling the shutdown endpoint. Check if the request handler validates user session, authentication tokens, or authorization headers before executing the shutdown command.Affected if The shutdown endpoint executes without requiring valid authentication credentials.
-
Confirm endpoint accessibility from untrusted networksTest accessing the shutdown endpoint from an unauthenticated external host over HTTPS. Observe whether the request reaches the handler without being blocked by authentication, IP restrictions, or network firewalls.Affected if An unauthenticated remote attacker can reach and trigger the shutdown endpoint over the network.
You are affected if your application exposes a shutdown function via HTTPS that can be triggered by any unauthenticated remote attacker who can reach the endpoint.
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 proper authorization checks requiring valid authentication before executing shutdown or administrative functions. Consider also adding CSRF protection and rate limiting on administrative endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47662 — 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-2021-47662 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