dbcve.org
Acuant Asureid SentinelApplication · Gbgplc

CVE-2022-48228

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 5.2.149 or later.
See remediation →
57/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
An issue was discovered in Acuant AsureID Sentinel before 5.2.149. It uses the root of the C: drive for the i-Dentify and Sentinel Installer log files, aka CORE-7362.

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

Acuant AsureID Sentinel before version 5.2.149 writes i-Dentify and Sentinel Installer log files to the root of the C: drive (C:\) instead of a proper application directory. This insecure file storage location could allow low-privileged users to potentially overwrite or manipulate files in a sensitive system location, leading to information disclosure or privilege escalation in certain attack scenarios.

MitigationUpgrade Acuant AsureID Sentinel to version 5.2.149 or later, which redirects log file output to an appropriate application directory rather than the C: drive root.

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 Asureid SentinelApplication
Affected:< 5.2.149

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
None
Availability
None

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

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 Acuant AsureID Sentinel is installed
    Look for the application in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check for the installation directory typically at C:\Program Files\Acuant or C:\Program Files (x86)\Acuant
    Affected if The application is found installed on the system
  2. Determine the installed version of Acuant AsureID Sentinel
    Check the Windows registry value DisplayVersion under the application's uninstall key, or examine the version information of the Sentinel executable in the installation directory
    Affected if The installed version is less than 5.2.149 (e.g., 5.2.100, 5.1.x, etc.)
  3. Inspect the C: drive root for i-Dentify log files
    Open File Explorer and navigate to C:\, or run 'dir C:\ i-Dentify*.log 2>nul' from an elevated command prompt, to look for log files named i-Dentify.log or similar
    Affected if Log files with i-Dentify in the name exist directly in C:\
  4. Inspect the C: drive root for Sentinel Installer log files
    Run 'dir C:\ Sentinel*Installer*.log 2>nul' or manually check C:\ for any log files containing 'Sentinel Installer' in the filename
    Affected if Log files with Sentinel Installer in the name exist directly in C:\

The system is affected if Acuant AsureID Sentinel is installed with a version lower than 5.2.149 AND log files from i-Dentify or Sentinel Installer are present in the C:\ root directory.

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

Upgrade Acuant AsureID Sentinel to version 5.2.149 or later, which redirects log file output to an appropriate application directory rather than the C: drive root.

Recommended fix High confidence

5.2.149

  1. Backup any existing Acuant AsureID Sentinel configuration and data
  2. Download Acuant AsureID Sentinel version 5.2.149 or later from the official Acuant website
  3. Install the updated version following standard installation procedures
  4. Verify that log files are no longer being written to the C: drive root directory
  5. Confirm the application functions normally after the update

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

Fix this in Acuant Asureid Sentinel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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