dbcve.org
Linkit Software Development KitApplication · Mediatek

CVE-2022-32665

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In Boa, there is a possible command injection due to improper input validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: A20220026; Issue ID: OSBNB00144124.

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 confidence

A command injection vulnerability exists in the Boa web server due to improper input validation. An attacker can exploit this to achieve remote privilege escalation without requiring any user interaction or elevated privileges. The vulnerability affects Boa implementations, commonly found in embedded systems and IoT devices.

MitigationApply the vendor patch (A20220026) to address the input validation issue, or upgrade to a patched version of Boa. If no patch is available, consider network segmentation or replacing Boa with a maintained web server solution.

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
Linkit Software Development KitApplication
Affected:< tlb7.3.258.100-p1-1555

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 if Boa web server is running on the system
    Check running processes for 'boa' or inspect the system web server configuration. On embedded systems, this may be in /proc or via 'ps' command if accessible.
    Affected if Boa web server process is found running on the system
  2. Determine the Mediatek Linkit SDK version
    Check the SDK version string on the device or firmware. This is typically found in system information files, build artifacts, or the firmware metadata. Look for version strings containing 'tlb' followed by version numbers.
    Affected if The SDK version is present and is lower than tlb7.3.258.100-p1-1555
  3. Identify the Boa web server version if directly accessible
    If the web interface is accessible, check any server version information or error pages. Alternatively, if you have access to the firmware or system files, locate the Boa binary and check its version or build information.
    Affected if Boa version cannot be determined or is from an unpatched Linkit SDK build prior to tlb7.3.258.100-p1-1555
  4. Verify network exposure of the web server
    Check network configuration to determine if the Boa web server is bound to external interfaces or is accessible from non-localhost addresses. Review firewall rules and network interface bindings.
    Affected if The Boa web server is accessible from network interfaces other than localhost/127.0.0.1

The system is affected if it runs a Mediatek Linkit SDK version prior to tlb7.3.258.100-p1-1555 with the Boa web server exposed on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (A20220026) to address the input validation issue, or upgrade to a patched version of Boa. If no patch is available, consider network segmentation or replacing Boa with a maintained web server solution.

Recommended fix High confidence

tlb7.3.258.100-p1-1555 or later

  1. Identify the current Linkit SDK version in use
  2. Obtain the fixed Linkit SDK version tlb7.3.258.100-p1-1555 or later from official MediaTek sources (corp.mediatek.com)
  3. Back up all existing configurations and firmware
  4. Apply the Linkit SDK upgrade following MediaTek's standard upgrade procedures
  5. Verify the Boa component has been updated to the patched version

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

Fix this in Linkit Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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