CVE-2024-1241
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 · uneditedWatchdog Antivirus v1.6.415 is vulnerable to a Denial of Service vulnerability by triggering the 0x80002014 IOCTL code of the wsdk-driver.sys driver.
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 confidenceWatchdog Antivirus v1.6.415 contains a kernel-mode driver vulnerability in wsdk-driver.sys. Sending IOCTL code 0x80002014 to the driver triggers a denial of service condition, likely causing a system crash or hang. This is a local privilege escalation DoS requiring an authenticated attacker to interact with the driver interface.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Watchdog Antivirus installationCheck for Watchdog Antivirus installation by looking in Programs and Features, or search for watchdog.exe in common program directories (C:\Program Files\Watchdog Antivirus\ or C:\Program Files (x86)\Watchdog Antivirus\)Affected if Watchdog Antivirus is found on the system
-
Check installed version numberLocate the watchdog.exe file, right-click and select Properties, then check the Details tab for the File Version. Alternatively, run 'wmic product get name,version' or check the uninstall registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if Version is 1.6.415 or falls within the affected version range around 1.6.415
-
Locate the vulnerable driver fileSearch for wsdk-driver.sys file on the system. Common paths include C:\Windows\System32\drivers\ or within the Watchdog Antivirus installation directory under a drivers subfolderAffected if wsdk-driver.sys file exists on the system
-
Verify driver is loadedOpen an elevated command prompt and run 'sc query wsdk-driver' or check Device Manager for hidden devices. Also check the driver file properties to confirm it matches the version associated with the vulnerable releaseAffected if The wsdk-driver.sys is present and loaded or loadable by the system
-
Check for IOCTL trigger attemptsEnable kernel debugging or use tools like Sysinternals Suite to monitor for IOCTL code 0x80002014 calls to the wsdk-driver. This requires driver communication monitoring capabilitiesAffected if IOCTL code 0x80002014 is being sent to wsdk-driver.sys (indicates active exploitation or testing)
-
Assess attacker access requirementsReview system logs and process monitoring to determine if an authenticated user has the ability to interact with the driver interface. This is a local privilege escalation requiring an authenticated attackerAffected if Non-admin users have access to invoke driver IOCTL calls
The system is affected if Watchdog Antivirus version 1.6.415 (or the affected version range) is installed AND the wsdk-driver.sys driver is present on the system, as the vulnerability exists in this driver component.
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 dataContact Watchdog Antivirus vendor for the latest patched version. If no patch is available, evaluate compensating controls such as restricting driver access or deploying an alternative endpoint protection solution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1241 — 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-1241 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