dbcve.org
CWE-404Weakness · CWE-404

CVE-2024-12227

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability, which was classified as problematic, was found in MSI Dragon Center up to 2.0.146.0. This affects the function MmUnMapIoSpace in the library NTIOLib_X64.sys of the component IOCTL Handler. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. Upgrading to version 2.0.148.0 is able to address this issue. It is recommended to upgrade the affected component.

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

A null pointer dereference vulnerability exists in the NTIOLib_X64.sys driver of MSI Dragon Center (versions up to 2.0.146.0). The vulnerability is in the MmUnMapIoSpace function when called through the IOCTL handler, allowing a local attacker to potentially cause denial of service or execute code.

MitigationUpgrade MSI Dragon Center to version 2.0.148.0 or later to address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Confirm MSI Dragon Center is installed
    Check for the application in Add/Remove Programs, or look in the default install directory (typically C:\Program Files\MSI\Dragon Center or C:\Program Files (x86)\MSI\Dragon Center). Also check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* for MSI Dragon Center entry.
    Affected if The application is not found on the system, then the system is not affected by this specific vulnerability.
  2. Check installed version of MSI Dragon Center
    Open Add/Remove Programs and locate MSI Dragon Center to view the version number, or check the version property of the executable at the install path (e.g., right-click Dragon Center.exe and select Properties > Details).
    Affected if The version is 2.0.146.0 or earlier (any version up to and including 2.0.146.0), the system falls within the affected version range.
  3. Locate the NTIOLib_X64.sys driver file
    Search for the file NTIOLib_X64.sys on the system. Common paths include C:\Program Files\MSI\Dragon Center\NTIOLib_X64.sys or C:\Program Files (x86)\MSI\Dragon Center\NTIOLib_X64.sys, or search the entire system drive.
    Affected if The driver file exists on the system and the installed MSI Dragon Center version is 2.0.146.0 or earlier.
  4. Verify driver is loaded or accessible
    Open Command Prompt as Administrator and run 'sc query NTIOLib_X64' to check if the driver service exists, or use 'driverquery /v | findstr NTIOLib' to see if the driver is loaded in memory.
    Affected if The driver service exists or is loaded in memory while the MSI Dragon Center version is 2.0.146.0 or earlier, indicating the vulnerable code path could be triggered.

The system is affected if MSI Dragon Center version 2.0.146.0 or earlier is installed AND the NTIOLib_X64.sys driver is present, as this combination contains the vulnerable MmUnMapIoSpace call in the IOCTL handler.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MSI Dragon Center to version 2.0.148.0 or later to address this vulnerability.

Recommended fix High confidence

2.0.148.0

  1. 1. Download MSI Dragon Center version 2.0.148.0 or later from the official MSI website (www.msi.com)
  2. 2. Uninstall the current version of MSI Dragon Center from the system
  3. 3. Install the newly downloaded version 2.0.148.0
  4. 4. Restart the computer if prompted to complete the installation

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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