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

> Attackers can bypass access controls on XML documents in OX Documents due to weak CRC32 hashing, allowing unauthorized access.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 27 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jjv6-934h-3qjm

## What is CVE-2021-28095?

CVE-2021-28095 is a medium-severity vulnerability in n/a, published on 27 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OX Documents before 7.10.5-rev5 has Incorrect Access Control for documents that contain XML structures because hash collisions can occur, due to use of CRC32.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Open-Xchange Open-Xchange Documents.

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

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

## Is CVE-2021-28095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28093](https://insights.sbomify.com/CVE-2021-28093/): Weak cryptography in n/a (medium 6.5)
- [CVE-2021-28094](https://insights.sbomify.com/CVE-2021-28094/): Weak cryptography in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-28095 is a medium-severity vulnerability in n/a, published on 27 Jul 2021. 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-28095 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-28095/ (Markdown: https://insights.sbomify.com/CVE-2021-28095/index.md)
```

## Sources

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

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