Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 709705 - (CVE-2011-2177) CVE-2011-2177 OpenOffice.org: InteVyDis Demo of OpenOffice 0day. Released with VulnDisco 8.8 pack (release date May,2009)
CVE-2011-2177 OpenOffice.org: InteVyDis Demo of OpenOffice 0day. Released wit...
Status: CLOSED CANTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
public=20110531,reported=20110531,sou...
: Security
Depends On:
Blocks: 711282
  Show dependency treegraph
 
Reported: 2011-06-01 08:44 EDT by Jan Lieskovsky
Modified: 2011-06-28 16:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-06-28 16:02:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2011-06-01 08:44:13 EDT
A new security flaw, potentially allowing execution of arbitrary code with
the privileges of the user running the OpenOffice.org suite tools has been
reported by the InteVyDis security researchers team:
[1] http://intevydis.com/oo_0day.html
[2] http://twitter.com/#!/legerov/status/75482755194032128

Note: Since no further detailed information is currently available about this
flaw, Red Hat Security Response Team is actively investigating the progress
done on this (at upstream and reporter side) and will update this record
with further information as soon as it is available.

Mitigation: Do not OpenOffice.org documents from untrusted sources.
Comment 1 Huzaifa S. Sidhpurwala 2011-06-03 01:54:15 EDT
This has been assigned CVE-2011-2177 as per:
http://thread.gmane.org/gmane.comp.security.oss.general/5161
Comment 2 Huzaifa S. Sidhpurwala 2011-06-07 06:18:05 EDT
Statement:

We do not currently plan to fix this issue due to the lack of further information about the flaw and its impact. If more information becomes available at a future date, we may revisit the issue.

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