Acu WizardApplication · Intel

CVE-2019-0138

HIGH · 7.8 CVSS v3.0 Published 2019-05-17
Fix available
A fix is available. Upgrade to after 12.0.0.129 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
Improper directory permissions in Intel(R) ACU Wizard version 12.0.0.129 and earlier may allow an authenticated user to potentially enable escalation of privilege 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

Intel(R) ACU Wizard versions 12.0.0.129 and earlier have improper directory permissions that allow authenticated users to modify directories they should not have write access to, potentially enabling local privilege escalation by replacing or modifying sensitive system files.

MitigationReview and correct directory permissions on the ACU Wizard installation directory and related system directories to enforce least-privilege access controls, restricting write access to authenticated non-admin users.

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
Acu WizardApplication
Affected:<= 12.0.0.129

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.0/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 Intel ACU Wizard is installed
    Look for the ACU Wizard installation directory, typically under Program Files or Program Files (x86) with 'Intel' or 'ACU' in the path. On Windows, also check Add/Remove Programs or the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Intel ACU Wizard' or similar.
    Affected if The software is found installed on the system.
  2. Determine installed version of ACU Wizard
    Locate the ACU Wizard executable (commonly named acu.exe, ACUWizard.exe, or similar) in the installation directory. Right-click the executable, select Properties, and check the Details tab for the Product Version. Alternatively, check version info in the Windows registry under the uninstall entry.
    Affected if The installed version is 12.0.0.129 or earlier.
  3. Inspect ACU Wizard installation directory permissions
    Right-click the ACU Wizard installation folder, select Properties, then go to the Security tab. Click Advanced to view detailed permissions. Check the permissions for authenticated users or non-admin user groups.
    Affected if Authenticated users or standard user accounts have Write or Full Control permissions to the ACU Wizard installation directory.
  4. Check for write access to sensitive system directories
    If ACU Wizard is installed in a system directory (such as Program Files, Windows, or System32), check whether standard users have write access to that location or can modify files within it.
    Affected if Non-admin users can write to directories that contain system binaries or sensitive configuration files.

The system is affected if Intel ACU Wizard version 12.0.0.129 or earlier is installed and non-privileged users have write access to the application directory or related system directories.

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.

From vendor data
Upgrade available Upgrade to a release after 12.0.0.129
Interim mitigation

Review and correct directory permissions on the ACU Wizard installation directory and related system directories to enforce least-privilege access controls, restricting write access to authenticated non-admin users.

Fix this in Acu Wizard Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2019-0138 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