CVE-2024-3745
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 · uneditedMSI Afterburner v4.6.6.16381 Beta 3 is vulnerable to an ACL Bypass vulnerability in the RTCore64.sys driver, which leads to triggering vulnerabilities like CVE-2024-1443 and CVE-2024-1460 from a low privileged user.
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 confidenceMSI Afterburner v4.6.6.16381 Beta 3 contains an ACL bypass vulnerability in the RTCore64.sys driver. The driver fails to properly enforce access control lists, allowing low-privileged users to communicate with the kernel-mode driver. This security control failure enables exploitation of additional vulnerabilities (CVE-2024-1443 and CVE-2024-1460) that would otherwise be restricted to higher-privilege contexts.
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.
-
Identify MSI Afterburner installation and versionCheck for MSI Afterburner installation directory (commonly C:\Program Files\MSI\Afterburner or C:\Program Files (x86)\MSI\Afterburner) and locate the version information in the application's about or properties window, or check the version of Afterburner.exeAffected if Installed version is 4.6.6.16381 Beta 3 or any earlier version of MSI Afterburner that includes the RTCore64.sys driver
-
Locate the RTCore64.sys driver fileSearch for RTCore64.sys in the MSI Afterburner installation directory (typically in the folder named 'SDK' or 'RTSS' within the Afterburner directory)Affected if The driver file RTCore64.sys exists on the system
-
Verify driver is loaded or loadableOpen Command Prompt as administrator and run 'sc query RTCore64' to check if the driver service exists and its status, or check Device Manager for hidden/system devicesAffected if The RTCore64 driver service exists or the driver is present in a location where it can be loaded by the application
-
Test driver access with standard user accountAttempt to access the driver device \Device\RTCore64 using a low-privilege account (non-administrator) - this can be verified by attempting to open the device via application that uses Afterburner functionality or by checking ACLs on the driver device if visibleAffected if A standard (non-admin) user account can successfully communicate with or access the RTCore64 kernel driver, indicating the ACL bypass is present
A user is affected if MSI Afterburner version 4.6.6.16381 Beta 3 or earlier is installed, the RTCore64.sys driver is present, and low-privileged accounts can communicate with the kernel driver (the ACL bypass condition exists).
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-provided patch/update to MSI Afterburner that corrects the ACL enforcement in RTCore64.sys. Until patch is available, consider restricting user access to Afterburner functionality or deploying compensating controls such as endpoint detection.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3745 — 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-3745 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