# CVE-2022-38582: Missing authorization in n/a

> Attackers can write arbitrary files via the anti-virus driver, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2022
- **Updated:** 2 May 2025
- **Also known as:** GHSA-m238-3frq-24mf

## What is CVE-2022-38582?

CVE-2022-38582 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect access control in the anti-virus driver wsdkd.sys of Watchdog Antivirus v1.4.158 allows attackers to write arbitrary files.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-38582?

It affects 1 product.


Products: Watchdog Anti-Virus.

## How do I fix CVE-2022-38582?

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

## Is CVE-2022-38582 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38582 exists.

## Other vulnerabilities in n/a

- [CVE-2022-38611](https://insights.sbomify.com/CVE-2022-38611/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-42045](https://insights.sbomify.com/CVE-2022-42045/): Code injection in n/a (medium 6.7)
- [CVE-2023-1446](https://insights.sbomify.com/CVE-2023-1446/): Watchdog Anti-Virus IoControlCode wsdk-driver.sys 0x80002008 denial of service (medium 5.5)
- [CVE-2023-1453](https://insights.sbomify.com/CVE-2023-1453/): Watchdog Anti-Virus IoControlCode wsdk-driver.sys 0x80002008 access control (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38582 and fix it if it is affected.

What it is: CVE-2022-38582 is a medium-severity missing authorization vulnerability in n/a, published on 4 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38582 exists.

Affected product: n/a. 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-2022-38582/ (Markdown: https://insights.sbomify.com/CVE-2022-38582/index.md)
```

## Sources

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

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