dbcve.org
Vc65 C1 FirmwareOperating system · Asus

CVE-2022-21933

HIGH · 7.8 CVSS v3.1 Published 2022-01-21
Fix available
A fix is available. Upgrade to 601 / 902 or later.
See remediation →
80/100
Remediation priority · High
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
ASUS VivoMini/Mini PC device has an improper input validation vulnerability. A local attacker with system privilege can use system management interrupt (SMI) to modify memory, resulting in arbitrary code execution for controlling the system or disrupting service.

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

ASUS VivoMini/Mini PC devices contain an improper input validation vulnerability allowing a local attacker with system privileges to exploit the System Management Interrupt (SMI) mechanism to modify memory and achieve arbitrary code execution, enabling full system control or service disruption.

MitigationApply vendor-supplied firmware updates from ASUS when available; until then, restrict physical and local administrative access to minimize the attack surface for this privilege-escalation vulnerability.

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
Vc65 C1 FirmwareOperating system
Affected:< 1302
Pb60v FirmwareOperating system
Affected:< 1302
Pb60g FirmwareOperating system
Affected:< 1302
Pb60s FirmwareOperating system
Affected:< 1302
Pa90 FirmwareOperating system
Affected:< 1401
Pb50 FirmwareOperating system
Affected:< 902
Pb60 FirmwareOperating system
Affected:< 1502
Pb61v FirmwareOperating system
Affected:< 601

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 exact ASUS Mini PC model
    Check the product label on the device or look up the model in the system BIOS/UEFI information screen (usually accessible via F2 or Delete during boot)
    Affected if The model is one of: Vc65 C1, Pb60v, Pb60g, Pb60s, Pa90, Pb50, Pb60, or Pb61v - otherwise this CVE does not apply
  2. Check the current firmware version
    Enter the BIOS/UEFI setup (press F2 or Delete during boot) and locate the BIOS version information, or use the ASUS Live Update utility if available on the running system
    Affected if The firmware version cannot be determined (unknown) - assume potentially affected if the model matches the affected list
  3. If the model is Vc65 C1, check if installed version is less than 1302
    Affected if Firmware version < 1302
  4. If the model is Pb60v, Pb60g, or Pb60s, check if installed version is less than 1302
    Affected if Firmware version < 1302
  5. If the model is Pa90, check if installed version is less than 1401
    Affected if Firmware version < 1401
  6. If the model is Pb50, check if installed version is less than 902
    Affected if Firmware version < 902

You are affected if your ASUS Mini PC model matches one of the listed vulnerable models AND the installed firmware version is below the corresponding threshold for that model.

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 601 / 902 / 1302 or later
Fixed in 6019021302
Interim mitigation

Apply vendor-supplied firmware updates from ASUS when available; until then, restrict physical and local administrative access to minimize the attack surface for this privilege-escalation vulnerability.

Recommended fix Moderate confidence

Firmware version 1302 or later for Vc65 C1/Pb60v/Pb60g/Pb60s; 1401 or later for Pa90; 902 or later for Pb50; 1502 or later for Pb60; 601 or later for Pb61v

  1. Identify the exact model of the ASUS VivoMini/Mini PC from the affected list (Vc65 C1, Pb60v, Pb60g, Pb60s, Pa90, Pb50, Pb60, Pb61v)
  2. Access the ASUS support website at https://www.asus.com/support/
  3. Enter the specific model number to locate the product support page
  4. Navigate to the Drivers & Utilities or BIOS/Firmware download section
  5. Download the latest firmware version for the model: Vc65 C1 upgrade to 1302 or later, Pb60v/Pb60g/Pb60s upgrade to 1302 or later, Pa90 upgrade to 1401 or later, Pb50 upgrade to 902 or later, Pb60 upgrade to 1502 or later, Pb61v upgrade to 601 or later
  6. Follow ASUS provided instructions to update the firmware, typically requiring the firmware file to be placed on a USB drive and the device to be rebooted into BIOS/UEFI update mode
  7. After firmware update, verify the installed firmware version matches the fixed release
Caveat Firmware updates on embedded devices can be irreversible; ensure stable power during update to avoid bricked device; some legacy functionality may change

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

Fix this in Vc65 C1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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