# CVE-2021-43444: Weak cryptography in n/a

> Attackers can forge signed document download URLs due to a weak default signing key, allowing unauthorized access to documents.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-6243-j7h8-mqf5

## What is CVE-2021-43444?

CVE-2021-43444 is a high-severity vulnerability in n/a, published on 23 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ONLYOFFICE all versions as of 2021-11-08 is affected by Incorrect Access Control. Signed document download URLs can be forged due to a weak default URL signing key.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-43444?

It affects 1 product.


Products: Onlyoffice Server.

## How do I fix CVE-2021-43444?

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

## Is CVE-2021-43444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43445](https://insights.sbomify.com/CVE-2021-43445/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2021-43449](https://insights.sbomify.com/CVE-2021-43449/): Server-side request forgery in n/a (high 8.1)
- [CVE-2021-43447](https://insights.sbomify.com/CVE-2021-43447/): Auth bypass in n/a (high 7.5)
- [CVE-2021-43446](https://insights.sbomify.com/CVE-2021-43446/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2021-43448](https://insights.sbomify.com/CVE-2021-43448/): Other in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43444 and fix it if it is affected.

What it is: CVE-2021-43444 is a high-severity vulnerability in n/a, published on 23 Jan 2023. 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-2021-43444 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-2021-43444/ (Markdown: https://insights.sbomify.com/CVE-2021-43444/index.md)
```

## Sources

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

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