Unencrypted saves via lost recovery encryption state
Published May 18, 2020 · Updated Nov 18, 2024
Cleartext storage in LibreOffice 6.3 before 6.3.6 and 6.4 before 6.4.3 causes recovered Microsoft Office files to save unencrypted. The recovery workflow preserves encryption in autosave and prompts for decryption, but then resets the subsequent save default to unencrypted for non-ODF formats. Exposure requires an encrypted non-ODF document, an application crash, successful password recovery, and a later user save, which can disclose document contents at rest.
Summary
What happened
Cleartext storage in LibreOffice 6.3 before 6.3.6 and 6.4 before 6.4.3 causes recovered Microsoft Office files to save unencrypted. The recovery workflow preserves encryption in autosave and prompts for decryption, but then resets the subsequent save default to unencrypted for non-ODF formats. Exposure requires an encrypted non-ODF document, an application crash, successful password recovery, and a later user save, which can disclose document contents at rest.
The record
- CVE
- CVE-2020-12801
- Published
- May 18, 2020
- Updated
- Nov 18, 2024
- Vendor
- The Document Foundation
- Product
- LibreOffice
- Classifications
- CWE-312, CWE-311
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 18, 2020CVE publishedPublication date reported by the CVE source.
- Nov 18, 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=6-3 series <6.3.6
- Affected versionversion=6-4 series <6.4.3
What conditions does exploitation require?
What is affected?
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