CVE-2021-20635
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 · uneditedImproper restriction of excessive authentication attempts in LOGITEC LAN-WH450N/GR allows an attacker in the wireless range of the device to recover PIN and access the network.
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 confidenceThe LOGITEC LAN-WH450N/GR wireless device contains an improper restriction of excessive authentication attempts vulnerability in its WPS (Wi-Fi Protected Setup) implementation. An attacker within wireless range can perform unlimited PIN authentication attempts, enabling brute-force recovery of the WPS PIN and subsequent unauthorized network access.
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 dataall versionsCVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/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 the device modelAccess the device's web administration interface (typically 192.168.1.1 or similar) and navigate to the status or device information page, or physically inspect the device label for the model numberAffected if The device model is LOGITEC LAN-WH450N/GR
-
Locate WPS configurationIn the device web admin interface, look for a WPS, Wi-Fi Protected Setup, or Wireless Security settings section. This is typically found under Wireless or Network settingsAffected if The WPS configuration menu is present and accessible on the device
-
Check if WPS is enabledIn the WPS settings section, verify whether WPS is currently turned on or enabled. This is usually indicated by a toggle, checkbox, or status field showing 'Enabled' or 'On'Affected if WPS is shown as enabled or turned on in the configuration
-
Check firmware versionIn the device web admin interface, look for a Firmware, Software, or Version section (often in Settings, Administration, or Status pages). Record the exact firmware version number displayedAffected if The device is running any firmware version on the LOGITEC LAN-WH450N/GR model (all versions are affected)
The environment is affected if the device is a LOGITEC LAN-WH450N/GR and WPS is enabled, since the vulnerability exists in all firmware versions and is exploitable only when WPS is active.
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 dataDisable WPS on the affected device if supported; otherwise, apply vendor firmware updates if available, or replace the device with a current model that receives security updates.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20635 — 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-20635 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