# CVE-2023-36622: Command injection in n/a

> Remote authenticated administrators can inject arbitrary OS commands via the timezone parameter in the websocket configuration endpoint.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2023
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-52rm-ch56-6jhr

## What is CVE-2023-36622?

CVE-2023-36622 is a high-severity command injection vulnerability in n/a, published on 5 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The websocket configuration endpoint of the Loxone Miniserver Go Gen.2 before 14.1.5.9 allows remote authenticated administrators to inject arbitrary OS commands via the timezone parameter.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Loxone Miniserver Go Gen 2 Firmware.

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

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

## Is CVE-2023-36622 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36623](https://insights.sbomify.com/CVE-2023-36623/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2023-36624](https://insights.sbomify.com/CVE-2023-36624/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36622 is a high-severity command injection vulnerability in n/a, published on 5 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36622 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-2023-36622/ (Markdown: https://insights.sbomify.com/CVE-2023-36622/index.md)
```

## Sources

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

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