Local code execution via unverified PE acceptance
Published Apr 10, 2025 · Updated Apr 10, 2025
Improper PE signature verification in MSI Center before 2.0.52.0 allows local users to execute code across a security boundary. MSI has not disclosed the component, executable-loading path, or validation logic that accepts an untrusted PE image without verifying its signature. Exploitation requires local access and high-complexity conditions but no prior privileges or user interaction; successful execution runs attacker-chosen code across the affected security boundary.
Summary
What happened
Improper PE signature verification in MSI Center before 2.0.52.0 allows local users to execute code across a security boundary. MSI has not disclosed the component, executable-loading path, or validation logic that accepts an untrusted PE image without verifying its signature. Exploitation requires local access and high-complexity conditions but no prior privileges or user interaction; successful execution runs attacker-chosen code across the affected security boundary.
The record
- CVE
- CVE-2025-27813
- Published
- Apr 10, 2025
- Updated
- Apr 10, 2025
- Vendor
- Micro-Star International Co., Ltd.
- Product
- MSI Center
- Classifications
- CWE-347, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2025CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.0.52.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo