dbcve.org
Acuant Acufill SdkApplication · Gbgplc

CVE-2022-48225

HIGH · 7.3 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 10.22.02.03 or later.
See remediation →
73/100
Remediation priority · Elevated

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
An issue was discovered in Acuant AcuFill SDK before 10.22.02.03. It is used to install drivers from several different vendors. The Gemalto Document Reader child installation process is vulnerable to DLL hijacking, because it attempts to execute (with elevated privileges) multiple non-existent DLLs out of a non-existent standard-user writable location.

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

The Acuant AcuFill SDK before 10.22.02.03 contains a DLL hijacking vulnerability in its Gemalto Document Reader child installation process. The installer runs with elevated privileges and attempts to load multiple non-existent DLLs from a standard-user writable directory that doesn't exist, allowing an attacker to place a malicious DLL in that location for privilege escalation.

MitigationUpgrade Acuant AcuFill SDK to version 10.22.02.03 or later to obtain the patched installer that no longer exhibits the vulnerable DLL search behavior.

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
Acuant Acufill SdkApplication
Affected:< 10.22.02.03

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify if Acuant AcuFill SDK is installed
    Check the installed programs list in Windows Control Panel > Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Acuant' or 'AcuFill'
    Affected if An entry for Gbgplc Acuant Acufill SDK or Acuant AcuFill SDK is found in the installed programs
  2. Determine the installed version of Acuant AcuFill SDK
    Locate the SDK installation directory (commonly under C:\Program Files\Acuant or similar) and check the version information of the main executable or DLL, or read the version from the uninstall registry entry
    Affected if The installed version is lower than 10.22.02.03 (for example, 10.x versions prior to 10.22.02.03)
  3. Verify presence of Gemalto Document Reader component
    Search the system for directories or files named 'Gemalto' or 'Document Reader' within the Acuant installation folder or related paths
    Affected if The Gemalto Document Reader child installation component is present on the system
  4. Check for the vulnerable DLL loading behavior
    During or prior to any installation or repair of the Acuant SDK, monitor DLL loading attempts using Process Monitor (ProcMon) filtered to the installer process, looking for attempts to load DLLs from user-writable locations that do not exist
    Affected if The installer process attempts to load non-existent DLLs from a standard-user writable directory path
  5. Review installer log files for DLL search path issues
    If available, examine installation logs from Acuant AcuFill SDK for warnings or errors related to missing DLLs or search paths, particularly during the Gemalto Document Reader component installation phase
    Affected if Logs show attempts to load DLLs from paths that are writable by standard users

A system is affected if the Acuant AcuFill SDK version is below 10.22.02.03 and the Gemalto Document Reader component is installed, as the installer will attempt to load DLLs from a user-writable directory allowing privilege escalation.

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

Upgrade Acuant AcuFill SDK to version 10.22.02.03 or later to obtain the patched installer that no longer exhibits the vulnerable DLL search behavior.

Recommended fix Moderate confidence

10.22.02.03

  1. Obtain Acuant AcuFill SDK version 10.22.02.03 or later from the official Acuant vendor (acuant.com)
  2. Review the official upgrade documentation provided by Acuant for the 10.22.02.03 release
  3. Test the new version in a non-production/staging environment to verify the DLL hijacking vulnerability is resolved
  4. Schedule a maintenance window for production deployment
  5. Deploy the upgraded Acuant AcuFill SDK version 10.22.02.03 to production systems
  6. Verify the Gemalto Document Reader child installation process no longer attempts to load DLLs from untrusted paths

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

Fix this in Acuant Acufill Sdk 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-48225 — 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-48225 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