Tablet Driver InstallerApplication · Wacom

CVE-2023-27529

HIGH · 7.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to 6.4.2-1 or later.
See remediation →
81/100
Remediation priority · High
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
Wacom Tablet Driver installer prior to 6.4.2-1 (for macOS) contains an improper link resolution before file access vulnerability. When a user is tricked to execute a small malicious script before executing the affected version of the installer, arbitrary code may be executed with the root privilege.

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

This is a Time-of-Check-Time-of-Use (TOCTOU) vulnerability in the Wacom Tablet Driver installer for macOS. The installer performs file access checks before operating on files, but fails to prevent symlink manipulation between those checks and operations. An attacker tricks a user into running a malicious script that creates/manipulates symlinks prior to installer execution, causing the installer (running with root privileges) to write files to arbitrary locations and achieve arbitrary code execution.

MitigationUpgrade Wacom Tablet Driver for macOS to version 6.4.2-1 or later. Users should be warned to avoid running untrusted scripts before executing software installers.

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
Tablet Driver InstallerApplication
Affected:< 6.4.2-1

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Check Wacom Tablet Driver version
    Open System Preferences or System Settings, locate Wacom Tablet settings, or check the installer package info. On macOS, you can also check the driver file info at /Library/Extensions/WacomTabletDriver.kext or via 'kextstat | grep Wacom' in Terminal
    Affected if The installed version is shown as anything earlier than 6.4.2-1 (for example, 6.4.1-x, 6.3.x, or any version number below 6.4.2-1)
  2. Verify installer version used
    If you have the original installer dmg or pkg file, right-click and select Get Info to view the version, or check the Wacom website download page for the version number of the installer you used
    Affected if The installer version is earlier than 6.4.2-1

You are affected if the installed Wacom Tablet Driver or its installer on macOS is any version lower than 6.4.2-1, as this is the version that patched the TOCTOU symlink manipulation flaw.

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

Upgrade Wacom Tablet Driver for macOS to version 6.4.2-1 or later. Users should be warned to avoid running untrusted scripts before executing software installers.

Recommended fix High confidence

Wacom Tablet Driver Installer 6.4.2-1 or later for macOS

  1. Download Wacom Tablet Driver Installer version 6.4.2-1 or later from the official Wacom website (www.wacom.com)
  2. Verify the downloaded installer integrity if checksums are provided
  3. Uninstall any currently installed vulnerable version of the Wacom Tablet Driver
  4. Run the updated installer (6.4.2-1 or later) to install the fixed version
  5. Restart your Mac if prompted to complete the installation

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

Fix this in Tablet Driver Installer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-27529 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