First published: Tue Feb 16 2010(Updated: )
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 document.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache OpenOffice | =2.0.4 | |
Apache OpenOffice | =2.4.1 | |
Apache OpenOffice | =3.1.1 | |
Debian Linux | =5.0 | |
Debian Linux | =4.0 | |
Ubuntu | =9.04 | |
Ubuntu | =8.10 | |
Ubuntu | =9.10 | |
Ubuntu | =8.04 | |
=2.0.4 | ||
=2.4.1 | ||
=3.1.1 | ||
=8.04 | ||
=8.10 | ||
=9.04 | ||
=9.10 | ||
=4.0 | ||
=5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-0136 has a moderate severity level, allowing potential execution of arbitrary macros.
To fix CVE-2010-0136, update OpenOffice.org to the latest version that properly enforces VBA macro security settings.
CVE-2010-0136 affects OpenOffice.org versions 2.0.4, 2.4.1, and 3.1.1.
Yes, CVE-2010-0136 can be exploited when a user opens a crafted document that bypasses VBA macro security settings.
A potential workaround for CVE-2010-0136 is to disable VBA macros in OpenOffice.org until an update is applied.