# CVE-2022-45482: Weak cryptography in Lazy Mouse

> Weak PIN requirements and lack of rate limiting allow remote attackers to brute force credentials and execute arbitrary commands.

- **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:** 2 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-2wh4-9v67-69x7

## What is CVE-2022-45482?

CVE-2022-45482 is a critical vulnerability in thisAAY Lazy Mouse, published on 2 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lazy Mouse server enforces weak password requirements and doesn't implement rate limiting, allowing remote unauthenticated users to easily and quickly brute force the PIN and execute arbitrary commands. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Lazy Mouse Project Lazy Mouse.

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

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

## Is CVE-2022-45482 being exploited?

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

## Other vulnerabilities in thisAAY Lazy Mouse

- [CVE-2022-45483](https://insights.sbomify.com/CVE-2022-45483/): Information disclosure in Lazy Mouse (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45482 is a critical vulnerability in thisAAY Lazy Mouse, published on 2 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-45482 in the wild and no public exploit code.

Affected product: thisAAY Lazy Mouse. 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-45482/ (Markdown: https://insights.sbomify.com/CVE-2022-45482/index.md)
```

## Sources

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

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