Bug 566013 (CVE-2010-0136) - CVE-2010-0136 openoffice.org: unenforced VBA macro security settings may lead to arbitrary macro execution
Summary: CVE-2010-0136 openoffice.org: unenforced VBA macro security settings may lead...
Alias: CVE-2010-0136
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://web.nvd.nist.gov/view/vuln/det...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-02-16 21:54 UTC by Vincent Danen
Modified: 2019-09-29 12:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-03-05 10:53:56 UTC

Attachments (Terms of Use)
sample document (133.50 KB, application/vnd.ms-excel)
2010-02-17 08:42 UTC, Caolan McNamara
no flags Details

Description Vincent Danen 2010-02-16 21:54:11 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2010-0136 to
the following vulnerability:

OpenOffice.org (OOo) 2.0.4, 2.4.1, and 3.1.1 does not properly enforce
Visual Basic for Applications (VBA) macro security settings, which
allows remote attackers to run arbitrary macros via a crafted


Comment 4 Caolan McNamara 2010-02-17 08:42:07 UTC
Created attachment 394694 [details]
sample document

Comment 5 Caolan McNamara 2010-02-17 08:47:42 UTC
This should be a ooo-build only problem in the 2.X.Y series. We don't use ooo-build for >= 1.X.Y so we shouldn't be affected by this fairly recent not-upstreamed-yet implementation-gone-awry. Sample document above can be used to verify that. i.e. loading it won't flip to sheet overview, etc. So this can be closed out in that case.

Comment 7 Tomas Hoger 2010-03-05 10:53:56 UTC
This flaw exists in the implementation of VBA macros support for OpenOffice.org.  This support is not (yet) part of upstream OpenOffice.org source, but only part of ooo-build / GO-OO patch set, which is not used in Red Hat OpenOffice.org packages version 2 and later.

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