# CVE-2022-45479: Missing authorization in PC Keyboard WiFi & Bluetooth

> Remote attackers can execute arbitrary code on the PC Keyboard app server without authentication due to missing authorization checks.

- **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:** 5 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-2wj7-33c2-h45r

## What is CVE-2022-45479?

CVE-2022-45479 is a critical missing authorization vulnerability in BEAppsMobile PC Keyboard WiFi & Bluetooth, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PC Keyboard allows remote unauthenticated users to send instructions to the server to execute arbitrary code without any previous authorization or authentication. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

It affects 1 product.


Products: Beappsmobile Pc Keyboard Wifi\&bluetooth.

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

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

## Is CVE-2022-45479 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45479 is a critical missing authorization vulnerability in BEAppsMobile PC Keyboard WiFi & Bluetooth, published on 5 Dec 2022. 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-2022-45479 in the wild and no public exploit code.

Affected product: BEAppsMobile PC Keyboard WiFi & Bluetooth. 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-45479/ (Markdown: https://insights.sbomify.com/CVE-2022-45479/index.md)
```

## Sources

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

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