dbcve.org
Fingerprint DriverApplication · Synaptics

CVE-2023-6482

MEDIUM · 5.2 CVSS v3.1 Published 2024-01-27
Fix available
A fix is available. Upgrade to 6.0.17.1103 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Use of encryption key derived from static information in Synaptics Fingerprint Driver allows an attacker to set up a TLS session with the fingerprint sensor and send restricted commands to the fingerprint sensor. This may allow an attacker, who has physical access to the sensor, to enroll a fingerprint into the template database.

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

The Synaptics Fingerprint Driver uses an encryption key derived from static information rather than dynamic/keyed secrets. This allows an attacker with physical access to the sensor to establish a TLS session and send restricted commands, potentially enabling unauthorized fingerprint enrollment into the device's template database.

MitigationApply vendor-supplied patches or firmware updates for the Synaptics Fingerprint Driver that implement proper dynamic key derivation. Until patched, limit physical access to affected devices and monitor for unauthorized biometric enrollment.

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
Fingerprint DriverApplication
Affected:>= 6.0.00.1103, < 6.0.17.1103

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

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. Confirm Synaptics Fingerprint Driver is installed
    Check system device manager or driver listing for Synaptics fingerprint sensor driver presence. On Windows: open Device Manager, look under 'Biometric devices' or search for 'Synaptics' in drivers. On Linux: check /proc/bus/input/devices or run 'lsmod | grep synaptics' if applicable.
    Affected if The driver is not present on the system, the vulnerability does not apply.
  2. Identify installed driver version
    Retrieve the driver version from the installed Synaptics Fingerprint Driver. On Windows: right-click the driver in Device Manager, select Properties, view Driver tab. On Linux: check driver module information via 'modinfo' or vendor-specific tools if available.
    Affected if Version cannot be determined - manual verification required through vendor documentation or system inventory tools.
  3. Compare version against affected range
    Verify if the installed version falls within >= 6.0.00.1103 AND < 6.0.17.1103. Parse the version number numerically - for example, version 6.0.5.1100 is in range, version 6.0.17.1103 is not in range (equal to upper bound), version 6.0.20.1100 is not in range.
    Affected if Installed version is >= 6.0.00.1103 AND < 6.0.17.1103 - the environment is affected by this vulnerability.

The environment is affected if the Synaptics Fingerprint Driver is installed and its version number is greater than or equal to 6.0.00.1103 but less than 6.0.17.1103.

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.0.17.1103 or later
Fixed in 6.0.17.1103
Interim mitigation

Apply vendor-supplied patches or firmware updates for the Synaptics Fingerprint Driver that implement proper dynamic key derivation. Until patched, limit physical access to affected devices and monitor for unauthorized biometric enrollment.

Recommended fix High confidence

6.0.17.1103 or later

  1. Check current Synaptics Fingerprint Driver version via Device Manager or the Synaptics control panel
  2. Download the latest version of the Synaptics Fingerprint Driver from the official Synaptics website or through your device manufacturer's support channel
  3. Run the driver installer with administrative privileges
  4. Restart the system to ensure the new driver is properly loaded
  5. Verify the installed driver version is 6.0.17.1103 or higher

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

Fix this in Fingerprint Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,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 $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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