Red Hat Bugzilla – Full Text Bug Listing
|Summary:||CVE-2011-2713 openoffice.org: Out-of-bounds read in DOC sprm parser|
|Product:||[Other] Security Response||Reporter:||Huzaifa S. Sidhpurwala <huzaifas>|
|Component:||vulnerability||Assignee:||Red Hat Product Security <security-response-team>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-10-05 06:41:16 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Huzaifa S. Sidhpurwala 2011-07-26 04:48:45 EDT
A heap-based buffer out-ouf-bounds read was found in the way OpenOffice.org imported certain Microsoft Word Binary File Format (.DOC) file.If a user opened a specially-crafted DOC file in OpenOffice.org suite tool (oowriter), it could lead to denial of service (oowriter executable crash), or possibly, execute arbitrary code with the privileges of the user running OpenOffice.org Writer. This has been assigned CVE-2011-2713.
Comment 12 Caolan McNamara 2011-09-16 12:00:13 EDT
Created attachment 523579 [details] combined backport to OpenOffice.org 3.2.1
Comment 13 Huzaifa S. Sidhpurwala 2011-10-05 06:38:42 EDT
This is public via: http://www.libreoffice.org/advisories/CVE-2011-2713/
Comment 14 Huzaifa S. Sidhpurwala 2011-10-05 06:40:46 EDT
It initially appeared that this flaw may be exploitable similar to CVE-2010-3452, where an OOB Read caused Arbitrary Code Execution. However in the case of this particular flaw, the junk data read is just parsed into an internal representation of properties and the maximum harm this should cause in application crash (Denial Of Service). Timeline: - Reported to email@example.com on 25-July-2011 - Recieved a reply (with firstname.lastname@example.org copied) on the same date - Release date changed with a few delays in between - Release on 5-Oct-2011 Statement: This issue results in an OOB read which is not exploitable for arbitrary code execution and can simply cause a crash. We do not consider this as a security issue.
Comment 15 Murray McAllister 2012-10-03 00:20:13 EDT
Acknowledgements: This issue was discovered by Huzaifa Sidhpurwala of the Red Hat Security Response Team.