High · published December 18, 2025
🚨 An unprivileged user can trigger a Blue Screen of Death (BSOD) using a sneaky IOCTL call — imagine your computer crashing as if it were a car that suddenly ran out of gas! 🔥 Think of it like a pesky kid pulling the fire alarm at a crowded event — causing chaos and panic without having any real authority to do so. In this case, the BSOD is the event being shut down abruptly, leaving everyone in the lurch. An attacker could cause complete system crashes on Windows machines, resulting in data loss and downtime. This could be absolutely devastating for any organization, as employees are left staring at a blue screen instead of getting their work done!
Think of it like a pesky kid pulling the fire alarm at a crowded event — causing chaos and panic without having any real authority to do so. In this case, the BSOD is the event being shut down abruptly, leaving everyone in the lurch. This vulnerability in DriveLock allows an unprivileged user to exploit an unterminated string through an IOCTL call, potentially causing a BSOD on affected versions 24.1 before 24.1.6, 24.2 before 24.2.7, and 25.1 before 25.1.5.
An attacker could cause complete system crashes on Windows machines, resulting in data loss and downtime. This could be absolutely devastating for any organization, as employees are left staring at a blue screen instead of getting their work done! Update DriveLock immediately to versions 24.1.6, 24.2.7, or 25.1.5 to patch this issue. Conduct a thorough review of user permissions to minimize risks associated with unprivileged actions. 🔒 You've got this! With these steps, you'll have your systems running smoothly and securely in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| drivelock/drivelock | ≥ 24.1, < 24.1.6 | 24.1.6 |
| drivelock/drivelock | ≥ 24.2, < 24.2.7 | 24.2.7 |
| drivelock/drivelock | ≥ 25.1, < 25.1.5 | 25.1.5 |