# CVE-2024-7788: Signatures in "repair mode" should not be trusted

> Attackers can forge digital signatures in LibreOffice repair mode, bypassing integrity checks and potentially misleading users about document authenticity.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2024
- **Updated:** 12 Oct 2024
- **Also known as:** BELL-CVE-2024-7788, DEBIAN-CVE-2024-7788, DLA-3915-1, DSA-5772-1, GHSA-62pp-53wf-pprq, UBUNTU-CVE-2024-7788, USN-7025-1

## What is CVE-2024-7788?

CVE-2024-7788 is a high-severity vulnerability in Libreoffice Libreoffice, published on 17 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper Digital Signature Invalidation  vulnerability in Zip Repair Mode of The Document Foundation LibreOffice allows Signature forgery vulnerability in LibreOfficeThis issue affects LibreOffice: from 24.2 before < 24.2.5.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2024-7788?

It affects 1 product.


Products: Libreoffice Libreoffice.

## How do I fix CVE-2024-7788?

Upgrade to a fixed version.

## Is CVE-2024-7788 being exploited?

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

## Other vulnerabilities in Libreoffice Libreoffice

- [CVE-2024-5261](https://insights.sbomify.com/CVE-2024-5261/): TLS certificate are not properly verified when utilizing LibreOfficeKit (critical 10.0)
- [CVE-2019-9855](https://insights.sbomify.com/CVE-2019-9855/): Windows 8.3 path equivalence handling flaw allows LibreLogo script execution (critical 9.8)
- [CVE-2018-14939](https://insights.sbomify.com/CVE-2018-14939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8358](https://insights.sbomify.com/CVE-2017-8358/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7882](https://insights.sbomify.com/CVE-2017-7882/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7788 and fix it if it is affected.

What it is: CVE-2024-7788 is a high-severity vulnerability in Libreoffice Libreoffice, published on 17 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-7788 in the wild and no public exploit code.

Affected product: Libreoffice Libreoffice. 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-2024-7788/ (Markdown: https://insights.sbomify.com/CVE-2024-7788/index.md)
```

## Sources

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

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