Macro execution via forgeable certificate identity prompt
Published Aug 5, 2024 · Updated Aug 5, 2024
Certificate-validation failure in LibreOffice 24.2 before 24.2.5 allows attackers to execute signed macros through crafted documents. The SfxObjectShell macro-security flow allowed hasTrustedScriptingSignature to add a signer after validation failed while emphasizing a forgeable Common Name. Exploitation requires a user to open the document and approve the invalid signer, after which its macros execute with that user's privileges.
Summary
What happened
Certificate-validation failure in LibreOffice 24.2 before 24.2.5 allows attackers to execute signed macros through crafted documents. The SfxObjectShell macro-security flow allowed hasTrustedScriptingSignature to add a signer after validation failed while emphasizing a forgeable Common Name. Exploitation requires a user to open the document and approve the invalid signer, after which its macros execute with that user's privileges.
The record
- CVE
- CVE-2024-6472
- Published
- Aug 5, 2024
- Updated
- Aug 5, 2024
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CAPEC-21, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24.2 <24.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo