dbcve.org
Cc3100 Software Development KitApplication · Ti

CVE-2021-22679

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
The affected product is vulnerable to an integer overflow while processing HTTP headers, 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 vulnerability in HTTP header processing within SimpleLink Wi-Fi firmware across multiple SDK versions (MSP432E4, CC32XX, CC13X0, CC13X2/CC26XX, CC3200, CC3100). The overflow can corrupt memory and enable remote code execution.

MitigationUpdate to patched SDK 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+.

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 TI SimpleLink SDK or device in use
    Determine which product family applies: CC3100, CC3200, CC13X0, CC13X2, CC26XX, CC32XX, or MSP432E4. Check project files, build configuration, or device documentation.
    Affected if The device or SDK is one of the seven product families listed in the affected versions.
  2. Locate the SDK version information
    For development environments, check the SDK installation directory name or version file. For deployed devices, check the firmware version string via UART debug, HTTP server info page, or device management interface.
    Affected if The SDK or firmware version cannot be determined or is not visible through standard interfaces.
  3. Compare the installed version against affected ranges
    Match your identified SDK version to 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 SDK version falls within or below any of these thresholds.
  4. Confirm HTTP server functionality is in use
    Verify that the device firmware includes HTTP server capability. Check if CONFIG_WLAN_STATION or similar Wi-Fi services are enabled, and if HTTP server modules are included in the build.
    Affected if HTTP server or Wi-Fi web server functionality is compiled into the firmware.

You are affected if your device runs firmware built with an SDK version that falls within or below the affected ranges AND the HTTP server feature is enabled.

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 to patched SDK 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+.

Recommended fix High confidence

Upgrade to at least CC13x0 SDK v4.10.03, CC13x2/CC26xx SDK v4.40.00, CC32xx SDK v4.40.00, MSP432E4 SDK v4.30.00 (or later), CC3100 SDK v1.4.0 (or later), CC3200 SDK v1.6.0 (or later)

  1. Identify the exact SimpleLink SDK version used in your product (check the SDK release notes or version file).
  2. Determine if the version falls within any of the vulnerable ranges: CC3100 SDK <= 1.3.0, CC3200 SDK <= 1.5.0, CC13x0 SDK < 4.10.03, CC13x2/CC26xx SDK < 4.40.00, CC32xx SDK <= 4.30.00.06, MSP432E4 SDK <= 4.20.00.12.
  3. Download the latest SimpleLink SDK for your device from the Texas Instruments website (e.g., SimpleLink CC13x0 SDK, CC13x2 SDK, CC26xx SDK, CC32xx SDK, MSP432E4 SDK, CC3100 SDK, CC3200 SDK).
  4. Upgrade the SDK to at least the following secure versions: CC13x0 SDK v4.10.03 or later; CC13x2/CC26xx SDK v4.40.00 or later; CC32xx SDK v4.40.00 or later; MSP432E4 SDK v4.30.00 (or later); CC3100 SDK v1.4.0 or later; CC3200 SDK v1.6.0 or later (or the most recent version available).
  5. Rebuild the firmware/application with the new SDK, ensuring all compiler flags and dependencies remain consistent.
  6. Perform regression testing, especially around HTTP header processing, to verify the vulnerability is resolved and no new issues are introduced.
  7. Deploy the updated firmware to devices.
Caveat Upgrading the SDK may require application code changes, review release notes for API changes, and re‑testing for compatibility with hardware.

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

Fix this in Cc3100 Software Development Kit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22679 — 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-22679 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