Bug 1507806 (CVE-2017-12608) - CVE-2017-12608 libreoffice: Out-of-bounds write in the WW8RStyle::ImportOldFormatStyles functionality
Summary: CVE-2017-12608 libreoffice: Out-of-bounds write in the WW8RStyle::ImportOldFo...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-12608
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1507808
Blocks: 1507560
TreeView+ depends on / blocked
 
Reported: 2017-10-31 08:21 UTC by Andrej Nemec
Modified: 2021-02-17 01:19 UTC (History)
6 users (show)

Fixed In Version: libreoffice 5.0.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-31 09:27:11 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrej Nemec 2017-10-31 08:21:19 UTC 
An exploitable out-of-bounds write vulnerability exists in the WW8RStyle::ImportOldFormatStyles functionality of Apache OpenOffice 4.1.3. A specially crafted doc file can cause a out-of-bounds write resulting in arbitrary code execution. An attacker can send/provide malicious doc file to trigger this vulnerability.

External References:

https://www.talosintelligence.com/reports/TALOS-2017-0301
https://www.openoffice.org/security/cves/CVE-2017-12608.html
https://www.libreoffice.org/about-us/security/advisories/CVE-2017-12608
Comment 1 Andrej Nemec 2017-10-31 08:23:14 UTC 
Created libreoffice tracking bugs for this issue:

Affects: fedora-all [bug 1507808]
Comment 2 David Tardon 2017-10-31 08:47:24 UTC 
Most likely fixed by https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff_plain;h=42a709d1ef647aab9a1c9422b4e25ecaee857aba , which would mean no Fedora version is vulnerable. Is there any reproducer?
Comment 3 David Tardon 2017-10-31 09:07:05 UTC 
Caolan confirms this is fixed by the mentioned commit, so no current Fedora is vulnerable.
Comment 4 Huzaifa S. Sidhpurwala 2017-10-31 09:24:49 UTC 
As per LibreOffice upstream advisory mentioned in comment 0, this issue is fixed in version 5.0.2, hence only the version shipped with Red Hat Enterprise Linux 6 is vulnerable.
Note You need to log in before you can comment on or make changes to this bug.