dbcve.org
Fingerprint ManagerApplication · Lenovo

CVE-2015-3321

MEDIUM · 6.7 CVSS v3.0 Published 2017-10-03
Fix available
A fix is available. Upgrade to after 8.01.41 or later.
See remediation →
69/100
Remediation priority · Elevated
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
Services and files in Lenovo Fingerprint Manager before 8.01.42 have incorrect ACLs, which allows local users to invalidate local checks and gain privileges via standard filesystem operations.

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

Lenovo Fingerprint Manager versions before 8.01.42 contain incorrect Access Control List (ACL) configurations on services and associated files, allowing local authenticated users to modify these components and bypass local security checks to escalate privileges to higher permission levels.

MitigationUpgrade Lenovo Fingerprint Manager to version 8.01.42 or later to obtain corrected ACL configurations that enforce proper filesystem permissions.

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 ManagerApplication
Affected:<= 8.01.41

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

CVSS:3.0/AV:L/AC:L/PR:H/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. Check if Lenovo Fingerprint Manager is installed
    Look for the application in Add/Remove Programs (Windows) or check common installation directories such as C:\Program Files\Lenovo\Fingerprint Manager or C:\Program Files (x86)\Lenovo\Fingerprint Manager
    Affected if The application directory or registry entry for Lenovo Fingerprint Manager exists on the system
  2. Determine the installed version
    Check the version of the fingerprint manager software. In Windows, right-click the executable (typically FingerprintManager.exe or similar in the installation folder), select Properties, and view the Details tab for the File Version. Alternatively, check the Windows registry under HKLM\SOFTWARE\Lenovo\Fingerprint Manager or HKLM\SOFTWARE\Wow6432Node\Lenovo\Fingerprint Manager for the Version value
    Affected if The installed version is 8.01.41 or earlier, or no version information or version information shows a build number lower than 42
  3. Inspect service ACL configuration
    Use the Windows icacls command or Security Properties dialog on the fingerprint manager service executable (typically in the installation directory, commonly named like FingerprintManager.exe or lfsservice.exe) to view the current ACL permissions
    Affected if Users with limited or standard privileges have Modify, Write, or Full Control permissions on the service executable, allowing them to replace or modify the binary
  4. Check associated file permissions
    Examine ACLs on all executable files and DLLs in the Lenovo Fingerprint Manager installation directory using icacls or file properties
    Affected if Standard or limited users have permissions to modify, write, or replace any executable files, DLLs, or configuration files in the application directory
  5. Verify service configuration
    Check the Windows service configuration for the fingerprint manager service using sc qc or services.msc to identify the service name, then examine the service binary path and its ACLs
    Affected if The service is configured to run with elevated privileges but the service binary is writable by non-privileged users, or the service has misconfigured permissions

A user is affected if Lenovo Fingerprint Manager version 8.01.41 or earlier is installed and the service executable or related files have overly permissive ACLs allowing standard users to modify them.

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.

From vendor data
Upgrade available Upgrade to a release after 8.01.41
Interim mitigation

Upgrade Lenovo Fingerprint Manager to version 8.01.42 or later to obtain corrected ACL configurations that enforce proper filesystem permissions.

Fix this in Fingerprint Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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