CVE-2024-50804
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 MSI Center Pro 2.1.37.0 allows a local attacker to execute arbitrary code via the Device_DeviceID.dat.bak file within the C:\ProgramData\MSI\One Dragon Center\Data folder
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 confidenceMSI Center Pro 2.1.37.0 has insecure file permissions on the Device_DeviceID.dat.bak backup file in C:\ProgramData\MSI\One Dragon Center\Data. A local attacker with file system access can modify this file to achieve arbitrary code execution with the privileges of the application.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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 checksWork through these to decide whether this CVE applies to you.
-
Verify MSI Center Pro is installedCheck for the presence of MSI Center Pro in the system by looking for the installation directory C:\ProgramData\MSI\One Dragon Center\ or checking Programs and Features for MSI Center ProAffected if The application is installed and the vulnerable file exists in the Data folder
-
Locate the vulnerable backup fileNavigate to C:\ProgramData\MSI\One Dragon Center\Data\ and check for the file named Device_DeviceID.dat.bakAffected if The file Device_DeviceID.dat.bak exists in that directory
-
Inspect file permissions on the backup fileRight-click the file, go to Properties > Security tab, and examine the permissions. Alternatively, run 'icacls C:\ProgramData\MSI\One Dragon Center\Data\Device_DeviceID.dat.bak' from an elevated command prompt to view ACLsAffected if Users or groups other than SYSTEM, Administrators, or the installing user have Write or Full Control permissions to this file
-
Check parent folder permissionsInspect permissions on C:\ProgramData\MSI\One Dragon Center\Data\ folder using icacls or folder Properties > Security tabAffected if Non-privileged users have Write or Modify access to the Data folder, allowing them to replace or tamper with the backup file
-
Verify application versionCheck the installed version of MSI Center Pro through Programs and Features, or look for version information in the application directory or executable metadataAffected if The installed version is MSI Center Pro 2.1.37.0 or earlier versions that contain the vulnerable file
A user is affected if MSI Center Pro version 2.1.37.0 or earlier is installed and the Device_DeviceID.dat.bak file exists with overly permissive access controls allowing non-privileged users to modify it.
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 proper access control lists (ACLs) to restrict write access to the backup file and folder, or update to a patched version of MSI Center Pro that fixes the permission vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50804 — 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-50804 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