dbcve.org
Acuant Acufill SdkApplication · Gbgplc

CVE-2022-48226

HIGH · 7.8 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 10.22.02.03 or later.
See remediation →
80/100
Remediation priority · High
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
An issue was discovered in Acuant AcuFill SDK before 10.22.02.03. During installation, an EXE gets executed out of C:\Windows\Temp. A standard user can create the path file ahead of time and obtain elevated code execution. Permissions need to be modified to prevent manipulation.

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 installer before version 10.22.02.03 executes an EXE file from the C:\Windows\Temp directory during the installation process. A standard (unprivileged) user can pre-create the target file path in Temp and inject malicious code, which then executes with elevated privileges during the installation, achieving privilege escalation.

MitigationThe vendor should modify the installer to avoid executing files from user-writable directories like Temp, use secure temporary file handling, and apply proper permissions. Organizations should restrict write access to C:\Windows\Temp and monitor for suspicious executable creation.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Acuant AcuFill SDK is installed
    Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Gbgplc\Acuant\AcuFill or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Gbgplc\Acuant\AcuFill, or look for the product in Add/Remove Programs
    Affected if The product is found on the system
  2. Check installed version number
    Query the version value from the registry keys above or right-click the installed executable and view Properties to find the File Version
    Affected if The installed version is lower than 10.22.02.03 (e.g., 10.21.x.x or earlier)
  3. Verify installation has occurred
    Check if the product installation directory exists under Program Files or Program Files (x86) and contains AcuFill SDK files
    Affected if Installation completed - the vulnerable installer has already been run
  4. Inspect C:\Windows\Temp for suspicious executables
    Open C:\Windows\Temp in File Explorer or run 'dir C:\Windows\Temp\*.exe' to list any executable files present in the Temp directory
    Affected if Unexpected or unrecognized .exe files exist in the Temp folder, which could indicate pre-existing malicious files or post-exploitation artifacts

If Acuant AcuFill SDK is installed with a version lower than 10.22.02.03, the installer was vulnerable to privilege escalation via Temp directory file injection.

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

The vendor should modify the installer to avoid executing files from user-writable directories like Temp, use secure temporary file handling, and apply proper permissions. Organizations should restrict write access to C:\Windows\Temp and monitor for suspicious executable creation.

Recommended fix High confidence

Acuant AcuFill SDK version 10.22.02.03 or later

  1. Obtain the fixed version of Acuant AcuFill SDK (version 10.22.02.03 or later) from the official Acuant vendor website
  2. Verify the download using official checksums or digital signatures provided by Acuant to ensure installer authenticity
  3. Uninstall any existing vulnerable version of Acuant AcuFill SDK
  4. Install the fixed version (10.22.02.03 or later) following standard installation procedures
  5. After installation, verify that the application functions correctly and no longer executes binaries from C:\Windows\Temp during setup

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-48226 — 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-48226 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