dbcve.org
QuickaccessApplication · Acer

CVE-2022-24286

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 2.01.3030 / 3.00.3038 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
Acer QuickAccess 2.01.300x before 2.01.3030 and 3.00.30xx before 3.00.3038 contains a local privilege escalation vulnerability. The user process communicates with a service of system authority through a named pipe. In this case, the Named Pipe is also given Read and Write rights to the general user. In addition, the service program does not verify the user when communicating. A thread may exist with a specific command. When the path of the program to be executed is sent, there is a local privilege escalation in which the service program executes the path with system 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

Acer QuickAccess contains a local privilege escalation where a user-accessible named pipe lacks proper access controls. The service running as SYSTEM does not verify user identity when processing commands sent through the named pipe, allowing any local user to send a program path that the service will execute with elevated privileges.

MitigationUpdate Acer QuickAccess to version 2.01.3030 or later for the 2.01.300x branch, or 3.00.3038 or later for the 3.00.30xx branch 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
QuickaccessApplication
Affected:>= 2.01.3000, < 2.01.3030>= 3.00.3000, < 3.00.3038

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. Locate Acer QuickAccess installation
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Acer\QuickAccess for the application folder
    Affected if Acer QuickAccess is present on the system
  2. Identify installed version
    Right-click the application in Programs and Features and select Properties, or check the version info in the QuickAccess executable file
    Affected if Version is 2.01.3000 through 2.01.3029 OR 3.00.3000 through 3.00.3037
  3. Verify vulnerable service exists
    Use Task Manager or services.msc to check for the Acer QuickAccess service running on the system
    Affected if The Acer QuickAccess service is running and the version falls within the affected ranges
  4. Confirm named pipe exposure
    Use Sysinternals PipeList or check with PowerShell Get-Process to identify named pipes created by the QuickAccess service
    Affected if Acer QuickAccess service is running and creates a named pipe accessible to all users, with version in affected range

A user is affected if Acer QuickAccess is installed with version 2.01.3000-2.01.3029 or 3.00.3000-3.00.3037, enabling an unprivileged local user to escalate via the unprotected named pipe.

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 2.01.3030 / 3.00.3038 or later
Fixed in 2.01.30303.00.3038
Interim mitigation

Update Acer QuickAccess to version 2.01.3030 or later for the 2.01.300x branch, or 3.00.3038 or later for the 3.00.30xx branch to remediate this vulnerability.

Recommended fix High confidence

Acer QuickAccess 2.01.3030 (for 2.01.3xxx branch) or 3.00.3038 (for 3.00.3xxx branch)

  1. 1. Identify the installed Acer QuickAccess version by checking Programs and Features or the application's About/Help section
  2. 2. For systems with QuickAccess version 2.01.3xxx: upgrade to version 2.01.3030 or later
  3. 3. For systems with QuickAccess version 3.00.3xxx: upgrade to version 3.00.3038 or later
  4. 4. Download the updated Acer QuickAccess installer from Acer's official support website (acer.com) or through the Acer QuickAccess auto-update feature if available
  5. 5. Run the installer with administrator privileges and complete the upgrade
  6. 6. Restart the computer to ensure the new service version is loaded
  7. 7. Verify the installed version matches or exceeds the fixed versions (2.01.3030 or 3.00.3038)
Caveat Standard upgrade risk - ensure user data is backed up before upgrading; the upgrade may require brief service interruption

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

Fix this in Quickaccess Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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