Kernel memory corruption via unchecked driver calls
Published Sep 12, 2024 · Updated Sep 12, 2024
Improper bounds checking in WibuKey before 6.70 allows local users to corrupt kernel memory through crafted driver calls. The WibuKey32.sys and WibuKey64.sys drivers fail to bounds-check buffers before performing attacker-controlled address writes. Low-privileged local access is required; successful writes can compromise the host, while network exploitation is unavailable.
Summary
What happened
Improper bounds checking in WibuKey before 6.70 allows local users to corrupt kernel memory through crafted driver calls. The WibuKey32.sys and WibuKey64.sys drivers fail to bounds-check buffers before performing attacker-controlled address writes. Low-privileged local access is required; successful writes can compromise the host, while network exploitation is unavailable.
The record
- CVE
- CVE-2024-45181
- Published
- Sep 12, 2024
- Updated
- Sep 12, 2024
- Vendor
- WIBU-SYSTEMS AG
- Product
- WibuKey
- Classifications
- CWE-119, CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2024CVE publishedPublication date reported by the CVE source.
- Sep 12, 2024Record 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 <6.70
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