# CVE-2021-38679: Improper Authentication in Kazoo Server


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5hf8-wqqm-3jx5

## What is CVE-2021-38679?

CVE-2021-38679 is a medium-severity vulnerability in QNAP Systems Inc. Kazoo Server, published on 11 Feb 2022. 

### Official description

An improper authentication vulnerability has been reported to affect QNAP NAS running Kazoo Server. If exploited, this vulnerability allows attackers to compromise the security of the system. We have already fixed this vulnerability in the following versions of Kazoo Server: Kazoo Server 4.11.22 and later

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-38679?

It affects 1 product.


Products: Qnap Kazoo Server.

## How do I fix CVE-2021-38679?

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

## Is CVE-2021-38679 being exploited?

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

## Other vulnerabilities in QNAP Systems Inc. Kazoo Server

- [CVE-2021-38680](https://insights.sbomify.com/CVE-2021-38680/): Reflected XSS in Kazoo Server (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38679 and fix it if it is affected.

What it is: CVE-2021-38679 is a medium-severity vulnerability in QNAP Systems Inc. Kazoo Server, published on 11 Feb 2022. 
Exploitation: There is no known exploitation of CVE-2021-38679 in the wild and no public exploit code.

Affected product: QNAP Systems Inc. Kazoo Server. 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-2021-38679/ (Markdown: https://insights.sbomify.com/CVE-2021-38679/index.md)
```

## Sources

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

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