# CVE-2024-1241: Watchdog Antivirus v1.6.415 - Denial of Service

> Attackers can cause a denial of service in Watchdog Antivirus by triggering a specific IOCTL code in the driver.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-57mj-8cw4-cm9w

## What is CVE-2024-1241?

CVE-2024-1241 is a medium-severity vulnerability in Watchdog Antivirus, published on 23 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Watchdog Antivirus v1.6.415 is vulnerable to a Denial of Service vulnerability by triggering the 0x80002014 IOCTL code of the wsdk-driver.sys driver.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-1241?


## How do I fix CVE-2024-1241?

No fix has been published for CVE-2024-1241 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1241 being exploited?

There is no known exploitation of CVE-2024-1241 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1241 and fix it if it is affected.

What it is: CVE-2024-1241 is a medium-severity vulnerability in Watchdog Antivirus, published on 23 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1241 in the wild and no public exploit code.

Affected product: Watchdog Antivirus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1241/ (Markdown: https://insights.sbomify.com/CVE-2024-1241/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1241
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1241
- OSV: https://osv.dev/vulnerability/CVE-2024-1241

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1241/
Summaries are generated and may contain mistakes; the official description above is the record.