dbcve.org
Linkit Software Development KitApplication · Mediatek

CVE-2022-32664

HIGH · 8.8 CVSS v3.1 Published 2023-01-03
Fix available
A fix is available. Upgrade to 7.3.293.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Config Manager, there is a possible command injection due to improper input validation. This could lead to remote escalation of privilege with User execution privileges needed. User interaction is needed for exploitation. Patch ID: A20220004; Issue ID: OSBNB00140929.

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

This is a command injection vulnerability in a Config Manager component caused by improper input validation. An attacker with user-level execution privileges and requiring user interaction can inject malicious commands through insufficiently validated input fields, potentially achieving privilege escalation to execute arbitrary code on the system.

MitigationApply vendor patch A20220004 immediately. Additionally, implement strict input validation and sanitization for all user-supplied parameters in the Config Manager, following secure coding practices such as allowlist validation and avoiding dynamic command construction.

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:< 7.3.293.0

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
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 checks

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

  1. Locate Linkit SDK installation
    Search for the Mediatek Linkit SDK installation directory or check common installation paths. Look for files or folders containing 'Linkit' or 'MediaTek' in the program directories.
    Affected if The SDK is found on the system.
  2. Determine installed SDK version
    Inspect version information in the SDK's metadata, about dialog, or version file. Check the file properties of the main SDK executable or the version tag in the installation manifest.
    Affected if The version is lower than 7.3.293.0.
  3. Verify Config Manager component presence
    Locate the Config Manager component within the SDK installation directory. This is typically found in the tools or utilities subfolder of the Linkit SDK.
    Affected if The Config Manager component exists and is accessible.
  4. Check execution context and privileges
    Review the environment where the SDK is deployed (development machine, build server, etc.) and verify what user-level privileges are assigned to processes running the Config Manager.
    Affected if The Config Manager runs with user-level execution privileges.

The environment is affected if the Mediatek Linkit SDK version is below 7.3.293.0 and the Config Manager component is present and executable with user-level privileges.

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 7.3.293.0 or later
Fixed in 7.3.293.0
Interim mitigation

Apply vendor patch A20220004 immediately. Additionally, implement strict input validation and sanitization for all user-supplied parameters in the Config Manager, following secure coding practices such as allowlist validation and avoiding dynamic command construction.

Recommended fix Moderate confidence

Linkit Software Development Kit 7.3.293.0 or later

  1. 1. Identify the currently installed Linkit SDK version by checking the SDK documentation or version file
  2. 2. Navigate to the official MediaTek developer resources or download portal at corp.mediatek.com
  3. 3. Download Linkit SDK version 7.3.293.0 or later from the official source
  4. 4. Back up any existing projects, configurations, and custom settings before upgrading
  5. 5. Uninstall or remove the current Linkit SDK installation
  6. 6. Install the new SDK version 7.3.293.0 following the standard installation procedure
  7. 7. Restore backed-up project files and configurations to the new installation
  8. 8. Verify the installation by checking the SDK version matches 7.3.293.0 or higher
Caveat Review SDK release notes for any API changes or migration requirements that may affect existing projects

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 the upgrade done

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-32664 — 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-32664 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