dbcve.org
Acuant Asureid SentinelApplication · Gbgplc

CVE-2022-48227

HIGH · 7.8 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 5.2.149 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 AsureID Sentinel before 5.2.149. It allows elevation of privileges because it opens Notepad after the installation of AssureID, Identify x64, and Identify x86, aka CORE-7361.

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 · moderate confidence

A local privilege escalation vulnerability in Acuant AsureID Sentinel versions before 5.2.149 allows an unprivileged user to gain elevated privileges through the application opening Notepad after installation of AssureID, Identify x64, and Identify x86 components.

MitigationUpgrade Acuant AsureID Sentinel to version 5.2.149 or later to remediate this vulnerability.

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
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. Check if Acuant AsureID Sentinel is installed
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the application in Add/Remove Programs. The application may be listed as 'Acuant AsureID Sentinel' or 'GBGplc Acuant AsureID Sentinel'.
    Affected if The application is found in installed programs on the system
  2. Identify the installed version of AsureID Sentinel
    In Registry Editor, check the 'DisplayVersion' value in the uninstall key for AsureID Sentinel. Alternatively, locate the Sentinel executable (commonly in Program Files or Program Files (x86) under an Acuant folder) and view its file properties to see the version.
    Affected if The displayed version number is lower than 5.2.149, or no version is displayed and the file properties show a version prior to 5.2.149
  3. Verify presence of Identify components
    Check if the 'Identify x64' and 'Identify x86' components are installed. These may be listed as separate entries in Add/Remove Programs, or check the installation directory for folders or executables containing 'Identify' in the name.
    Affected if Both Identify x64 and Identify x86 components are present alongside the main AsureID Sentinel installation
  4. Compare against the affected version range
    Using the version found in step 2, compare it numerically to 5.2.149. Note that version comparison should treat 5.2.149 as the first safe version - any version below this threshold (e.g., 5.2.148, 5.1.200, 4.x) is affected.
    Affected if The installed version is 5.2.148 or any earlier version, AND the Identify x64/x86 components are installed

A user is affected if Acuant AsureID Sentinel is installed with a version lower than 5.2.149 and the Identify x64 and Identify x86 components are present on the system.

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 to remediate this vulnerability.

Recommended fix Moderate confidence

5.2.149 or later

  1. 1. Identify the current version of Acuant AsureID Sentinel installed on the system
  2. 2. Obtain the updated version (5.2.149 or later) from the official Acuant vendor or authorized distribution channel
  3. 3. Backup any existing Acuant AsureID Sentinel configurations and data as a precautionary measure
  4. 4. Uninstall the current version of Acuant AsureID Sentinel
  5. 5. Install version 5.2.149 or the latest available version from Acuant
  6. 6. Verify the installation completed successfully
  7. 7. Reconfigure any necessary settings and validate the application functions correctly

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

Fix this in Acuant Asureid Sentinel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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