# CVE-2023-36669: Missing authorization in n/a

> Remote attackers can gain arbitrary control of the HVAC system by impersonating the touch panel due to missing authentication on critical functions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2023
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-qcf4-5rjw-q56c

## What is CVE-2023-36669?

CVE-2023-36669 is a critical missing authorization vulnerability in n/a, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authentication for a Critical Function within the Kratos NGC Indoor Unit (IDU) before 11.4 allows remote attackers to obtain arbitrary control of the IDU/ODU system. Any attacker with layer-3 network access to the IDU can impersonate the Touch Panel Unit (TPU) within the IDU by sending crafted TCP requests to the IDU.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-36669?

It affects 1 product.


Products: Kratosdefense Ngc Indoor Unit Firmware.

## How do I fix CVE-2023-36669?

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

## Is CVE-2023-36669 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36670](https://insights.sbomify.com/CVE-2023-36670/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36669 and fix it if it is affected.

What it is: CVE-2023-36669 is a critical missing authorization vulnerability in n/a, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36669 in the wild and no public exploit code.

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-2023-36669/ (Markdown: https://insights.sbomify.com/CVE-2023-36669/index.md)
```

## Sources

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

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