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

> Improper access control in Carel Boss Mini allows attackers to bypass security restrictions and access protected resources.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-5w9h-x2v4-5xm7

## What is CVE-2022-34827?

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

### Official description

Carel Boss Mini 1.5.0 has Improper Access Control.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Carel Boss Mini Firmware.

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

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

## Is CVE-2022-34827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-3643](https://insights.sbomify.com/CVE-2023-3643/): Boss Mini document file inclusion (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34827 is a high-severity missing authorization vulnerability in n/a, published on 18 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-34827 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-34827/ (Markdown: https://insights.sbomify.com/CVE-2022-34827/index.md)
```

## Sources

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

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