CVE-2021-37570
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 IEEE 1905 protocols. (Affected Chipsets MT7603E, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915; Affected Software Versions 2.0.2; Out-of-bounds read).
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 confidenceAn out-of-bounds read vulnerability exists in MediaTek microchips (MT7603E, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915) when handling IEEE 1905 protocols. The vulnerability allows memory contents to be read beyond allocated buffer boundaries, potentially exposing sensitive data. Affected NETGEAR devices running software version 2.0.2 and earlier are vulnerable.
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= 2.0.2= 2.0.2= 2.0.2= 2.0.2= 2.0.2= 2.0.2= 2.0.2CVSS 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 MediaTek chipset modelCheck the device hardware specifications, bootloader, or system information to determine if the device uses one of the following MediaTek chipsets: MT7603E, MT7613, MT7615, MT7622, MT7628, MT7629, or MT7915Affected if The device does not use one of the listed MediaTek chipsets
-
Check firmware versionAccess the device's administrative interface or use commands such as 'cat /proc/version', 'nvram show', or vendor-specific CLI tools to retrieve the installed firmware versionAffected if The firmware version is 2.0.2 or earlier
-
Verify NETGEAR software versionFor NETGEAR devices, check the web administration panel or run 'grep' on configuration files to identify the software version running on the deviceAffected if The NETGEAR software version is 2.0.2 or earlier
-
Confirm IEEE 1905 protocol is enabledInspect the device's network configuration, wireless settings, or protocol-specific configuration files to determine if the IEEE 1905 protocol (used for smart home device discovery) is actively enabledAffected if IEEE 1905 protocol support is enabled on the device
A user is affected if the device contains a MediaTek MT7603E, MT7613, MT7615, MT7622, MT7628, MT7629, or MT7915 chipset with firmware version 2.0.2 or earlier and has IEEE 1905 protocol functionality enabled.
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 dataApply vendor-supplied firmware updates for affected MediaTek-based devices. If no update is available, consider network segmentation to limit exposure of affected devices and disable IEEE 1905 protocol features where not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37570 — 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-37570 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