# CVE-2024-6472: Ability to trust not validated macro signatures removed in high security mode > Attackers can bypass macro signature validation in LibreOffice, potentially executing malicious code if users ignore warnings. - **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:** 5 Aug 2024 - **Updated:** 5 Aug 2024 - **Also known as:** ALSA-2024:5583, ALSA-2024:5598, DEBIAN-CVE-2024-6472, DSA-5737-1, GHSA-w6mm-86qp-2r3q, MGASA-2024-0320, RHSA-2024:5583, RHSA-2024:5584, RHSA-2024:5598, RHSA-2024:5599, RHSA-2024:5601, RHSA-2024:5607, RHSA-2024:5608, RHSA-2024:5886, RLSA-2024:5598, UBUNTU-CVE-2024-6472, USN-6962-1 ## What is CVE-2024-6472? CVE-2024-6472 is a high-severity vulnerability in Libreoffice Libreoffice, published on 5 Aug 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 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. Weakness: CWE-295 (Improper Certificate Validation) ## Which versions are affected by CVE-2024-6472? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `autocorr-af` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-bg` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ca` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-cs` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-da` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-de` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-en` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-es` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-fa` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-fi` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-fr` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ga` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-hr` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-hu` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-is` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-it` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ja` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ko` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-lb` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-lt` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-mn` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-nl` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-pl` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-pt` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ro` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-ru` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-sk` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-sl` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-sr` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-sv` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-tr` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-vi` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `autocorr-zh` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-base` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-calc` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-core` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-data` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-draw` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | | `libreoffice-emailmerge` | AlmaLinux:8 | All versions | 1:6.4.7.2-18.el8_10.alma.1 | Products: Libreoffice Libreoffice. ## How do I fix CVE-2024-6472? Upgrade to a fixed version. ## Is CVE-2024-6472 being exploited? There is no known exploitation of CVE-2024-6472 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-6472 and fix it if it is affected. What it is: CVE-2024-6472 is a high-severity vulnerability in Libreoffice Libreoffice, published on 5 Aug 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-6472 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-6472/ (Markdown: https://insights.sbomify.com/CVE-2024-6472/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6472 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6472 - OSV: https://osv.dev/vulnerability/CVE-2024-6472 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-6472/ Summaries are generated and may contain mistakes; the official description above is the record.