Elan Match On Chip Fpr Solution FirmwareOperating system · Emc

CVE-2024-0454

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-12

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

66/100

Remediation priority · Elevated

No privileges Zero-click

Official description

NVD · unedited

ELAN Match-on-Chip FPR solution has design fault about potential risk of valid SID leakage and enumeration with spoof sensor. This fault leads to that Windows Hello recognition would be bypass with cloning SID to cause broken account identity. Version which is lower than 3.0.12011.08009(Legacy)/3.3.12011.08103(ESS) would suffer this risk on DELL Inspiron platform.

Technical summary

dbcve analysis · moderate confidence

ELAN Match-on-Chip fingerprint sensor has a design flaw allowing valid SID (Security Identifier) leakage and enumeration via spoofed sensor. This enables attackers to bypass Windows Hello authentication by cloning the fingerprint sensor's SID, breaking account identity verification. The vulnerability affects ELAN FPR driver versions below 3.0.12011.08009 (Legacy) or 3.3.12011.08103 (ESS) on Dell Inspiron platforms.

MitigationUpdate ELAN fingerprint driver/firmware to version 3.0.12011.08009 or higher for Legacy, or 3.3.12011.08103 or higher for ESS. Verify Windows Hello authentication functions correctly after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Elan Match On Chip Fpr Solution FirmwareOperating system

Affected:= 3.0.12011.08009= 3.3.12011.08103

CVSS breakdown

From the vector

Attack vector: Physical
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

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

Am I affected?

dbcve checks

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

Check for ELAN fingerprint sensor presence

Open Device Manager, expand 'Biometric devices' or look for 'ELAN' under 'Human Interface Devices'. Alternatively, run: wmic path Win32_PnPSignedDriver where "Description like '%ELAN%FPR%' or Description like '%Fingerprint%'" get DeviceName, DriverVersion, Status

Affected if No ELAN fingerprint sensor is found - the system is not vulnerable because the affected component is not present
Retrieve ELAN fingerprint driver version

In Device Manager, right-click the ELAN fingerprint device, select Properties, then the Driver tab. Note the Driver Version. Or use: powershell Get-PnpDevice -Class Biometric | Where-Object {$_.FriendlyName -match 'ELAN'} | Format-List InstanceId, Status, DriverVersion

Affected if Driver version cannot be determined or the sensor is not ELAN - need to manually verify the specific driver/firmware version
Compare against Legacy threshold version

If the driver is identified as 'Legacy' variant, compare the version string to 3.0.12011.08009. Versions below this (e.g., 3.0.x.x below 08009) are affected. Note: version comparison should treat the full numeric string as a version number.

Affected if Version is below 3.0.12011.08009 - the system is vulnerable to SID leakage and Windows Hello bypass
Compare against ESS threshold version

If the driver is identified as 'ESS' variant, compare the version string to 3.3.12011.08103. Versions below this (e.g., 3.3.x.x below 08103) are affected.

Affected if Version is below 3.3.12011.08103 - the system is vulnerable to SID leakage and Windows Hello bypass
Verify Windows Hello fingerprint authentication is configured

Go to Windows Settings > Accounts > Sign-in options. Check if 'Windows Hello Fingerprint' is set up or enabled under 'Biometric sign-in'. The vulnerability only has impact if Windows Hello uses fingerprint authentication.

Affected if Windows Hello fingerprint is enabled with a vulnerable ELAN sensor version - the system is at risk of authentication bypass via SID cloning

The system is affected if it contains an ELAN Match-on-Chip fingerprint sensor with firmware/driver version below 3.0.12011.08009 (Legacy) or 3.3.12011.08103 (ESS), and Windows Hello fingerprint authentication is configured.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update ELAN fingerprint driver/firmware to version 3.0.12011.08009 or higher for Legacy, or 3.3.12011.08103 or higher for ESS. Verify Windows Hello authentication functions correctly after the update.

Recommended fix Moderate confidence

Firmware version 3.0.12011.08009 or higher for Legacy branch; 3.3.12011.08103 or higher for ESS branch

Contact Elan Microelectronics (www.emc.com.tw) or your device manufacturer (e.g., Dell for Inspiron platforms) to obtain the firmware update.
Verify the current fingerprint sensor firmware version through Windows Device Manager or the vendor's diagnostic tool.
Apply the firmware update following the vendor's specific instructions, which typically involve running a firmware update utility while the system is powered on and connected to AC power.
After updating, verify the new firmware version matches or exceeds the fixed release (Legacy: 3.0.12011.08009 or higher; ESS: 3.3.12011.08103 or higher).
Ensure Windows Hello is re-enrolled with a new fingerprint template to prevent any potential cloned SID from being used.

Caveat Firmware updates may require re-enrollment of fingerprints in Windows Hello; backup any critical Windows Hello credentials before updating

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

Fix this in Elan Match On Chip Fpr Solution Firmware Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

github.comThird Party Advisory
www.emc.com.twNot Applicable
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0454 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-0454?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Elan Match On Chip Fpr Solution Firmware

Remediation

Need this fixed?

Fix this in Elan Match On Chip Fpr Solution Firmware 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-0454 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References