# CVE-2022-45170: Weak cryptography in n/a

> A malicious user can decrypt files without the key via a cryptographic flaw in the vDesk API, exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-hx37-3fvj-x3vr

## What is CVE-2022-45170?

CVE-2022-45170 is a medium-severity vulnerability in n/a, published on 14 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in LIVEBOX Collaboration vDesk through v018. A Cryptographic Issue can occur under the /api/v1/vencrypt/decrypt/file endpoint. A malicious user, logged into a victim's account, is able to decipher a file without knowing the key set by the user.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Liveboxcloud Vdesk.

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

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

## Is CVE-2022-45170 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45173](https://insights.sbomify.com/CVE-2022-45173/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-45174](https://insights.sbomify.com/CVE-2022-45174/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-45172](https://insights.sbomify.com/CVE-2022-45172/): Missing authorization in n/a (critical 9.8)
- [CVE-2022-45171](https://insights.sbomify.com/CVE-2022-45171/): File upload in n/a (high 8.8)
- [CVE-2022-45178](https://insights.sbomify.com/CVE-2022-45178/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45170 is a medium-severity vulnerability in n/a, published on 14 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45170 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-2022-45170/ (Markdown: https://insights.sbomify.com/CVE-2022-45170/index.md)
```

## Sources

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

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