dbcve.org
Driver \& Support AssistantApplication · Intel

CVE-2023-25073

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 23.4.33 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 access control in some Intel(R) DSA software before version 23.4.33 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 · moderate confidence

Improper access control vulnerability in Intel Data Streaming Accelerator (DSA) software versions prior to 23.4.33 allows an authenticated local user to potentially cause denial of service. The vulnerability stems from insufficient access control checks within the DSA software, enabling a local attacker with valid credentials to trigger a DoS condition.

MitigationUpgrade Intel DSA software to version 23.4.33 or later to remediate this vulnerability. Since the issue requires authenticated local access, ensure proper access controls and least-privilege principles are applied until the patch is deployed.

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
Driver \& Support AssistantApplication
Affected:< 23.4.33

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. Locate Intel Driver & Support Assistant installation
    Open Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Intel*Driver*Support*Assistant*'}
    Affected if The software is listed as installed and the version is below 23.4.33
  2. Check installed DSA software version via command line
    Run 'dsa_config -v' or 'C:\Program Files\Intel\Driver and Support Assistant\dsa_version.exe' if those executables exist on the system
    Affected if The reported version number is lower than 23.4.33
  3. Verify DSA service is running
    Open Services console and check if 'Intel Data Streaming Accelerator' service exists and is in a running state, or run 'Get-Service *DSA*' in PowerShell
    Affected if The DSA service exists and is running, combined with a version below 23.4.33 indicates exposure
  4. Identify running DSA processes
    Open Task Manager or run 'Get-Process | Where-Object {$_.ProcessName -like '*dsa*'}' in PowerShell
    Affected if DSA-related processes are active on the system with a vulnerable version

You are affected if Intel Driver & Support Assistant or Intel DSA software is installed with a version lower than 23.4.33 and the DSA component is active 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 23.4.33 or later
Fixed in 23.4.33
Interim mitigation

Upgrade Intel DSA software to version 23.4.33 or later to remediate this vulnerability. Since the issue requires authenticated local access, ensure proper access controls and least-privilege principles are applied until the patch is deployed.

Recommended fix High confidence

23.4.33 or later

  1. Open Intel Driver & Support Assistant on the affected system
  2. Click on the menu or settings to check the current version number
  3. Ensure the version is 23.4.33 or higher. If lower, an update is needed.
  4. Launch Intel Driver & Support Assistant and allow it to check for updates, or manually download the latest version from the official Intel support website
  5. Follow the on-screen prompts to install the update
  6. Restart the application if prompted and verify the version now shows 23.4.33 or later

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

Fix this in Driver \& Support Assistant Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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