CVE-2024-37726
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 · uneditedInsecure Permissions vulnerability in Micro-Star International Co., Ltd MSI Center v.2.0.36.0 allows a local attacker to escalate privileges via the Export System Info function in MSI.CentralServer.exe
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 confidenceIn MSI Center v2.0.36.0, the Export System Info function in MSI.CentralServer.exe contains insecure file or directory permissions that allow a local unprivileged attacker to manipulate the function and escalate privileges to higher permissions on the system.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check if MSI Center is installed and its versionOpen Programs and Features (appwiz.cpl) or check the installation directory for MSI Center. Look for version 2.0.36.0 or compare your installed version to this reference.Affected if MSI Center version 2.0.36.0 is installed or the installed version matches/contains this version number.
-
Locate MSI.CentralServer.exeSearch for the file MSI.CentralServer.exe in typical installation paths such as C:\Program Files\MSI\MSI Center or C:\Program Files (x86)\MSI\MSI Center, or use the command: dir /s C:\MSI.CentralServer.exeAffected if The file MSI.CentralServer.exe exists on the system.
-
Check file permissions on MSI.CentralServer.exeRight-click MSI.CentralServer.exe, select Properties, go to the Security tab, and examine the permissions for Users or authenticated users. Alternatively, use icacls "path\to\MSI.CentralServer.exe" to list permissions.Affected if Users or non-admin accounts have Write, Modify, or Full Control permissions on this executable.
-
Verify if the Export System Info feature existsLaunch MSI Center and look for an Export System Info or System Information export function within the application interface, or check the application logs for related activity.Affected if The Export System Info feature is present and accessible to the current user.
If MSI Center version 2.0.36.0 is installed, MSI.CentralServer.exe exists with weak permissions allowing modification by unprivileged users, and the Export System Info feature is accessible, the system is likely affected by this privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch when available. Until then, restrict physical/local access to the affected system, limit user account privileges, and review file permissions on MSI.CentralServer.exe and related components.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37726 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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