dbcve.org
Acuant Acufill SdkApplication · Gbgplc

CVE-2022-48224

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 installed with insecure permissions (full write access within Program Files). Standard users can replace files within this directory that get executed with elevated privileges, leading to a complete arbitrary code execution (elevation of privileges).

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 version 10.22.02.03 is installed in Program Files with overly permissive file permissions (full write access), allowing standard (non-privileged) users to modify or replace executable files in the installation directory. These files are subsequently executed with elevated (administrator/system) privileges, enabling arbitrary code execution with privilege escalation.

MitigationUpdate to Acuant AcuFill SDK version 10.22.02.03 or later which implements proper permission restrictions, or manually remediate by restricting write access to the installation directory to Administrators only using Windows ACL tools.

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. Locate Acuant AcuFill SDK installation
    Check if the Acuant AcuFill SDK is installed on the system by searching for the product in Program Files (typically C:\Program Files\ or C:\Program Files (x86)\). Look for a folder named 'Acuant' or 'Acufill' or 'Gbgplc Acuant Acufill SDK'.
    Affected if The software is found installed on the system.
  2. Identify the installed version
    Right-click the main executable or DLL in the installation folder, select Properties, and view the Version tab to obtain the product version. Alternatively, open the file in a text editor if it is an XML or manifest file that lists the version.
    Affected if The installed version is less than 10.22.02.03.
  3. Examine directory permissions
    Right-click the Acuant installation folder in Program Files, select Properties, then go to the Security tab. Click on 'Users' or 'Everyone' and check the permissions under 'Allow'. Verify if the 'Modify' or 'Full control' permission is granted.
    Affected if Standard (non-privileged) users have Write, Modify, or Full Control permissions on the installation directory.
  4. Verify executable replaceability
    As a standard (non-admin) user account, attempt to create or modify a file in the Acuant installation directory, or attempt to rename an executable file within that folder.
    Affected if The operation succeeds, confirming standard users can modify files in the directory.

A system is affected if Acuant AcuFill SDK version 10.22.02.03 or earlier is installed and the installation directory grants Write or Modify permissions to standard (non-privileged) users.

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

Update to Acuant AcuFill SDK version 10.22.02.03 or later which implements proper permission restrictions, or manually remediate by restricting write access to the installation directory to Administrators only using Windows ACL tools.

Recommended fix High confidence

10.22.02.03 or later

  1. Obtain Acuant AcuFill SDK version 10.22.02.03 or later from the official Acuant vendor channels
  2. Backup any existing Acuant AcuFill SDK installation and configuration
  3. Uninstall the vulnerable version of Acuant AcuFill SDK
  4. Install the fixed version (10.22.02.03 or later) of Acuant AcuFill SDK
  5. Verify the installation completed successfully and the application functions correctly
  6. Confirm that the directory permissions have been corrected (restrict write access for standard users in the Program Files installation directory)

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

Fix this in Acuant Acufill Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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