Bug 2013151 (CVE-2021-25634) - CVE-2021-25634 libreoffice: Timestamp Manipulation with Signature Wrapping
Summary: CVE-2021-25634 libreoffice: Timestamp Manipulation with Signature Wrapping
Alias: CVE-2021-25634
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 2014215 2014216
Blocks: 2013154
TreeView+ depends on / blocked
Reported: 2021-10-12 08:53 UTC by Sandipan Roy
Modified: 2022-05-11 21:45 UTC (History)
4 users (show)

Fixed In Version: LibreOffice 7.0.6, LibreOffice 7.1.2
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in LibreOffice, where it inserted a signing timestamp. This flaw allows LibreOffice to present a valid signature due to the altered signing time. The highest threat from this vulnerability is to confidentiality and integrity.
Clone Of:
Last Closed: 2022-05-11 21:45:31 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:1766 0 None None None 2022-05-10 13:20:04 UTC

Description Sandipan Roy 2021-10-12 08:53:21 UTC
An Improper Certificate Validation vulnerability in LibreOffice allowed an attacker to modify a digitally signed ODF document to insert an additional signing time timestamp which LibreOffice would incorrectly present as a valid signature signed at the bogus signing time.

Comment 2 Garrett Tucker 2021-10-14 15:53:06 UTC
RHEL 8.6.0 and below are all affected by this flaw. RHEL 9 uses an updated version which is not exposed to the flaw. LibreOffice allowed for the ability to insert a signing timestamp which allowed for LibreOffice to show a valid signature due to the altered signing time.

Comment 4 errata-xmlrpc 2022-05-10 13:20:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2022:1766 https://access.redhat.com/errata/RHSA-2022:1766

Comment 5 Product Security DevOps Team 2022-05-11 21:45:29 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.