dbcve.org
Cc3100 Software Development KitApplication · Ti

CVE-2021-22671

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-07
Fix available
A fix is available. Upgrade to 4.10.03 / 4.40.00 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Multiple integer overflow issues exist while processing long domain names, 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 confidence

Integer overflow vulnerabilities in SimpleLink Wi-Fi SDKs occur when processing excessively long domain names during network operations. The overflow can corrupt memory allocation sizes, leading to buffer overflows that enable remote code execution without authentication.

MitigationUpdate affected TI SimpleLink Wi-Fi SDKs to versions beyond those specified (MSP432E4: v4.20.00.12+, CC32XX: v4.30.00.06+, CC13X0: v4.10.03+, CC13X2/CC26XX: v4.40.00+, CC3200: v1.5.0+, CC3100: v1.3.0+), then recompile and deploy updated firmware to all affected IoT/embedded devices.

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
Cc3100 Software Development KitApplication
Affected:<= 1.3.0
Cc3200 Software Development KitApplication
Affected:<= 1.5.0
Simplelink Cc13x0 Software Development KitApplication
Affected:< 4.10.03
Simplelink Cc13x2 Software Development KitApplication
Affected:< 4.40.00
Simplelink Cc26xx Software Development KitApplication
Affected:< 4.40.00
Simplelink Cc32xx Software Development KitApplication
Affected:<= 4.30.00.06
Simplelink Msp432e4 Software Development KitApplication
Affected:<= 4.20.00.12

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the SDK version used to build the firmware
    Locate the build documentation, release notes, or SDK installation directory. Check firmware metadata or version strings that may embed the SDK version. Look for files like version.h, build_info, or release notes in the project.
    Affected if The SDK version cannot be determined or is older than the fixed versions.
  2. Compare SDK version against affected ranges for CC3100/CC3200
    If using CC3100 SDK, verify version is greater than 1.3.0. If using CC3200 SDK, verify version is greater than 1.5.0.
    Affected if CC3100 SDK version is <= 1.3.0 or CC3200 SDK version is <= 1.5.0.
  3. Compare SDK version against affected ranges for CC13x0
    If using CC13x0 SimpleLink SDK, verify version is >= 4.10.03.
    Affected if CC13x0 SDK version is less than 4.10.03.
  4. Compare SDK version against affected ranges for CC13x2/CC26xx
    If using CC13x2 or CC26xx SimpleLink SDK, verify version is >= 4.40.00.
    Affected if CC13x2 or CC26xx SDK version is less than 4.40.00.
  5. Compare SDK version against affected ranges for CC32xx/MSP432E4
    If using CC32xx SDK, verify version is greater than 4.30.00.06. If using MSP432E4 SDK, verify version is greater than 4.20.00.12.
    Affected if CC32xx SDK version is <= 4.30.00.06 or MSP432E4 SDK version is <= 4.20.00.12.
  6. Determine if firmware performs network operations with domain names
    Review the firmware source code or binary for DNS resolution, HTTP client, MQTT, or other network client functionality that resolves or uses domain names. Check network configuration or stack initialization code.
    Affected if Firmware uses network features that process domain names and SDK version is in the affected range.

A device is affected if the firmware was built using one of the listed SDK versions at or below the specified thresholds AND the firmware performs network operations involving domain name resolution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.10.03 / 4.40.00 or later
Fixed in 4.10.034.40.00
Interim mitigation

Update affected TI SimpleLink Wi-Fi SDKs to versions beyond those specified (MSP432E4: v4.20.00.12+, CC32XX: v4.30.00.06+, CC13X0: v4.10.03+, CC13X2/CC26XX: v4.40.00+, CC3200: v1.5.0+, CC3100: v1.3.0+), then recompile and deploy updated firmware to all affected IoT/embedded devices.

Recommended fix High confidence

CC3100 SDK >= 1.3.1, CC3200 SDK >= 1.5.1, CC13x0 SDK >= 4.10.03, CC13x2/CC26xx SDK >= 4.40.00, CC32xx SDK >= 4.30.00.07, MSP432e4 SDK >= 4.20.00.13

  1. 1. Identify which SimpleLink SDK(s) are in use from the list: CC3100 SDK, CC3200 SDK, CC13x0 SDK, CC13x2 SDK, CC26xx SDK, CC32xx SDK, or MSP432e4 SDK
  2. 2. For CC3100 SDK: upgrade to version 1.3.1 or later
  3. 3. For CC3200 SDK: upgrade to version 1.5.1 or later
  4. 4. For Simplelink CC13x0 SDK: upgrade to version 4.10.03 or later
  5. 5. For Simplelink CC13x2 SDK: upgrade to version 4.40.00 or later
  6. 6. For Simplelink CC26xx SDK: upgrade to version 4.40.00 or later
  7. 7. For Simplelink CC32xx SDK: upgrade to version 4.30.00.07 or later
  8. 8. For Simplelink MSP432e4 SDK: upgrade to version 4.20.00.13 or later
Caveat Minor - SDK updates typically maintain backward compatibility, but test thoroughly to ensure no behavioral changes in network domain name handling

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cc3100 Software Development Kit Scoped from the published advisory
  • Consultation12.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
76.0 hours of engineering $13,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $21,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22671 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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