CVE-2021-22673
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 · uneditedThe affected product is vulnerable to stack-based buffer overflow while processing over-the-air firmware updates from the CDN server, which may allow an attacker to remotely execute code on the SimpleLink Wi-Fi (MSP432E4 SDK: v4.20.00.12 and prior, CC32XX SDK v4.30.00.06 and prior, CC13X0 SDK versions prior to v4.10.03, CC13X2 and CC26XX SDK versions prior to v4.40.00, CC3200 SDK v1.5.0 and prior, CC3100 SDK v1.3.0 and prior).
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 confidenceA stack-based buffer overflow vulnerability exists in Texas Instruments SimpleLink Wi-Fi SDKs when processing over-the-air firmware updates from a CDN server. The lack of proper bounds checking during firmware download allows an attacker to overflow a stack buffer, potentially enabling remote code execution.
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<= 1.3.0<= 1.5.0< 4.10.03< 4.40.00< 4.40.00<= 4.30.00.06<= 4.20.00.12CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 TI SimpleLink SDK in useLocate the SDK installation directory or check project dependencies to determine which TI SimpleLink SDK (CC3100, CC3200, CC13x0, CC13x2, CC26xx, CC32xx, or MSP432E4) is being used in your development environment or firmware build.Affected if The project uses any of the affected SDK product lines listed in the CVE.
-
Determine the installed SDK versionCheck the SDK version information, typically found in the SDK release notes, version headers, or package manifest file. Compare your installed version against the affected ranges: CC3100 SDK <=1.3.0, CC3200 SDK <=1.5.0, CC13x0 SDK <4.10.03, CC13x2 SDK <4.40.00, CC26xx SDK <4.40.00, CC32xx SDK <=4.30.00.06, MSP432E4 SDK <=4.20.00.12.Affected if Your installed SDK version falls within any of these vulnerable version ranges.
-
Verify if OTA firmware update feature is enabledInspect your firmware configuration files and build settings to determine whether the over-the-air (OTA) firmware update feature is compiled into your device firmware. Look for configuration options related to firmware updates or OTA processing.Affected if OTA firmware update support is enabled in your firmware build.
-
Check CDN firmware update configurationExamine your device or application configuration to see if the firmware update mechanism is configured to retrieve updates from a CDN server, as the vulnerability is triggered when processing OTA updates from a CDN source.Affected if Your devices are configured to receive firmware updates from a CDN server source.
You are affected if your firmware uses any of the vulnerable SDK versions AND has OTA firmware update functionality enabled to fetch updates from a CDN server.
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 data4.10.034.40.00
Update affected SDKs to patched versions (MSP432E4 SDK v4.20.00.13+, CC32XX SDK v4.30.00.07+, CC13X0 SDK v4.10.03+, CC13X2/CC26XX SDK v4.40.00+, CC3200 SDK v1.5.1+, CC3100 SDK v1.3.1+) and rebuild/deploy updated firmware to all affected devices.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22673 — 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-22673 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