This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 658259 - (CVE-2010-4253) CVE-2010-4253 OpenOffice.org: heap based buffer overflow in PPT import
CVE-2010-4253 OpenOffice.org: heap based buffer overflow in PPT import
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,source=redhat,report...
: Security
Depends On: 642184 642185 642200 642201 804532
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-29 15:00 EST by Marc Schoenefeld
Modified: 2016-03-04 06:58 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-21 05:32:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Marc Schoenefeld 2010-11-29 15:00:17 EST
Marc Schoenefeld discovered a heap based buffer overflow in
OpenOffice.org 3.X, when imported certain Microsoft PowerPoint
files (PPT). If a user opened a specially crafted PPT file,
it could lead to applicable crash or possibly execution of
arbitrary code,  with the privileges of the user running
OpenOffice.org Impress.


This has been assigned CVE-2010-4253
Comment 5 Huzaifa S. Sidhpurwala 2011-01-26 22:52:52 EST
Public via:
http://www.openoffice.org/security/cves/CVE-2010-4253.html
Comment 6 errata-xmlrpc 2011-01-28 08:02:28 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0182 https://rhn.redhat.com/errata/RHSA-2011-0182.html
Comment 7 errata-xmlrpc 2011-01-28 10:24:54 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0183 https://rhn.redhat.com/errata/RHSA-2011-0183.html

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