dbcve.org
Quickassist TechnologyApplication · Intel

CVE-2024-31153

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 2.2.0-0012 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
Improper input validation for some Intel(R) QuickAssist Technology software before version 2.2.0 may allow an authenticated user to potentially enable denial of service via local access.

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

Improper input validation in Intel QuickAssist Technology software before version 2.2.0 allows an authenticated local user to trigger a denial of service condition. The vulnerability stems from insufficient validation of input parameters, which can be exploited by a local attacker with valid credentials.

MitigationUpgrade Intel QuickAssist Technology software to version 2.2.0 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
Quickassist TechnologyApplication
Affected:< 2.2.0-0012

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Intel QuickAssist Technology is installed
    Check for QAT software installation. On Linux, look for /usr/lib*/libqat* or run 'ls /usr/local/intel/QAT*' or check package manager. On Windows, check Program Files for Intel QuickAssist Technology folder or review installed software list.
    Affected if Intel QuickAssist Technology software is not present on the system, the vulnerability does not apply.
  2. Determine installed QAT software version
    Run the QAT version command if available, such as 'qat_engine -v' or check version information in the installation directory. Alternatively, inspect version strings in QAT library files using 'strings libqat* | grep -i version' in the install directory.
    Affected if Version is blank, unknown, or falls below 2.2.0-0012.
  3. Confirm QAT service or driver is active
    Check if QAT kernel modules are loaded (run 'lsmod | grep qat' on Linux) or if the QAT service is running (check Windows services for QuickAssist). The vulnerability requires the software to be running to be exploitable.
    Affected if The QAT software is running as a service, daemon, or loaded driver.
  4. Check for local user authentication configuration
    Review QAT authentication settings in configuration files (typically in /etc/ or the QAT config directory). Verify whether local user accounts have valid credentials configured for QAT access.
    Affected if Local authenticated users exist with valid QAT credentials, enabling the attack vector.

The environment is affected if Intel QuickAssist Technology software is installed with a version below 2.2.0-0012 and the software or its drivers are actively running, allowing an authenticated local user to exploit the input validation flaw.

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.2.0-0012 or later
Fixed in 2.2.0-0012
Interim mitigation

Upgrade Intel QuickAssist Technology software to version 2.2.0 or later to remediate this vulnerability.

Recommended fix High confidence

2.2.0-0012 or later

  1. 1. Identify the current version of Intel QuickAssist Technology software installed on the system
  2. 2. If the installed version is earlier than 2.2.0-0012, obtain the updated version 2.2.0-0012 or later from Intel's official distribution channels
  3. 3. Follow Intel's standard upgrade procedure for QuickAssist Technology software, ensuring proper backups of existing configurations
  4. 4. After upgrade, verify the new version is running and test that QuickAssist functionality operates normally

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

Fix this in Quickassist Technology Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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