CVE-2021-37584
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 · uneditedMediaTek microchips, as used in NETGEAR devices through 2021-11-11 and other devices, mishandle the WPS (Wi-Fi Protected Setup) protocol. (Affected Chipsets MT7603E, MT7610, MT7612, MT7613, MT7615, MT7620, MT7622, MT7628, MT7629, MT7915; Affected Software Versions 7.4.0.0; Out-of-bounds write).
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 vulnerability is an out-of-bounds write in the WPS (Wi-Fi Protected Setup) protocol implementation in multiple MediaTek chipsets used in NETGEAR and other devices. This memory corruption issue occurs during WPS message processing, potentially allowing remote attackers to execute arbitrary code or cause denial of service via malformed WPS requests.
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= 7.4.0.0= 7.4.0.0= 7.4.0.0= 7.4.0.0= 7.4.0.0= 7.4.0.0= 7.4.0.0= 7.4.0.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 the MediaTek chipset modelAccess the device admin interface or check device documentation/specifications to determine the chipset (Mt7603e, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, or Mt7628)Affected if The device uses any of the listed MediaTek chipsets (Mt7603e, Mt7610, Mt7612, Mt7613, Mt7615, Mt7620, Mt7622, Mt7628)
-
Check the firmware versionLocate the firmware version in the device admin interface (typically under Status, Firmware Upgrade, or About section) and compare to 7.4.0.0Affected if The firmware version equals exactly 7.4.0.0 on an affected chipset
-
Confirm WPS is enabledAccess the wireless settings or WPS configuration page in the device admin interface and verify the WPS feature is turned onAffected if WPS is enabled on the device - this is required for the vulnerability to be exploitable
-
Verify device uses WPS functionalityCheck if any wireless clients have ever used WPS to connect, or if WPS push button or PIN methods are configured in the wireless settingsAffected if WPS is actively configured or has been used - the vulnerability triggers during WPS message processing
A device is affected if it contains one of the listed MediaTek chipsets (Mt7603e through Mt7628) with firmware version 7.4.0.0 and has WPS enabled or configured.
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 affected devices if possible; apply firmware updates from MediaTek or device vendors (NETGEAR) when available; if no update exists, consider network isolation or device replacement.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37584 — 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-37584 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