CVE-2021-37583
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 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 confidenceOut-of-bounds write vulnerability in MediaTek microchips mishandling IEEE 1905 protocol messages. The flaw allows potential remote code execution or denial of service via specially crafted IEEE 1905 protocol packets on the local network.
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
- 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 MediaTek chip modelCheck the device hardware specifications, FCC filings, or device teardown reports to determine if the device uses a MediaTek chip from the following models: Mt7603e, Mt7613, Mt7615, Mt7622, Mt7628, Mt7629, or Mt7915.Affected if The device does not contain one of the listed MediaTek chip models.
-
Check MediaTek firmware versionAccess the device's administrative interface or firmware diagnostics page, or use vendor-specific tools to query the installed firmware version on the MediaTek chip. Compare the version against the affected version: 2.0.2.Affected if The installed MediaTek firmware version is exactly 2.0.2.
-
Verify IEEE 1905 protocol statusInspect the device's network settings, protocol configuration, or wireless advanced settings to determine whether IEEE 1905 (also known as IEEE 1905.1a) protocol support is enabled or active. This protocol is often used for smart home/hybrid mesh networking features.Affected if IEEE 1905 protocol support is enabled or active on the device.
-
Assess local network exposureReview network topology and firewall rules to determine if untrusted devices can send broadcast or multicast packets on the same local network segment as the affected device.Affected if The device is accessible to untrusted devices on the local network segment that could send specially crafted IEEE 1905 packets.
The device is likely affected if it contains one of the listed MediaTek chips (Mt7603e, Mt7613, Mt7615, Mt7622, Mt7628, Mt7629, or Mt7915) running firmware version 2.0.2 with IEEE 1905 protocol enabled and accessible to potential attackers on the local network.
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 from MediaTek and device manufacturers (NETGEAR, etc.) when available. Prioritize patching LAN-facing devices and consider network segmentation to limit exposure to the IEEE 1905 protocol attack surface.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.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 $5,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37583 — 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-37583 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