# CVE-2022-37401: Apache OpenOffice Weak Master Keys

> Weak master key entropy allows attackers with local access to brute force and decrypt stored web connection passwords.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-468w-rc5f-76wx

## What is CVE-2022-37401?

CVE-2022-37401 is a high-severity vulnerability in Apache Openoffice, published on 13 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Apache OpenOffice supports the storage of passwords for web connections in the user's configuration database. The stored passwords are encrypted with a single master key provided by the user. A flaw in OpenOffice existed where master key was poorly encoded resulting in weakening its entropy from 128 to 43 bits making the stored passwords vulnerable to a brute force attack if an attacker has access to the users stored config. This issue affects: Apache OpenOffice versions prior to 4.1.13. Reference: CVE-2022-26307 - LibreOffice

Weakness: CWE-331 (Insufficient Entropy)

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

It affects 1 product.


Products: Apache Openoffice.

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

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

## Is CVE-2022-37401 being exploited?

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

## Other vulnerabilities in Apache Openoffice

- [CVE-2014-3524](https://insights.sbomify.com/CVE-2014-3524/): Command injection in n/a (critical 9.3)
- [CVE-2010-3450](https://insights.sbomify.com/CVE-2010-3450/): Path traversal in n/a (critical 9.3)
- [CVE-2010-3451](https://insights.sbomify.com/CVE-2010-3451/): Use after free in n/a (critical 9.3)
- [CVE-2010-3452](https://insights.sbomify.com/CVE-2010-3452/): Use after free in n/a (critical 9.3)
- [CVE-2010-3453](https://insights.sbomify.com/CVE-2010-3453/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37401 is a high-severity vulnerability in Apache Openoffice, published on 13 Aug 2022. 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-37401 in the wild and no public exploit code.

Affected product: Apache Openoffice. 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-37401/ (Markdown: https://insights.sbomify.com/CVE-2022-37401/index.md)
```

## Sources

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

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