Summary: | <app-office/openoffice-3.2.1-r1: code execution (CVE-2010-0395) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Robin Johnson <robbat2> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chithanh, fedotov.i.f, gentoo.cart9, shiningarcanine, spatz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.openoffice.org/security/cves/CVE-2010-0395.html | ||
Whiteboard: | B2 [glsa] | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 340917, 345309 | ||
Bug Blocks: |
Description
Robin Johnson
![]() ![]() ![]() ![]() RC1 is in the tree (though masked). Keeping this open for the final release. Unfortunately I'll be on vacation the next two weeks, so 3.2.1 will be late, I'm afraid... RC2 was released today. It is available in an overlay, but unfortunately, the overlay interferes with existing things that are installed on my system. Firefox is the most prominent example, which it wants to downgrade. It would be nice to have the ebuild in the tree bumped to RC2, although I took a look at it and I do not think it is as simple as changing its name to RC2 and putting it in a local overlay. Official 3.2.1 is out. OOo 3.2.1 is in the tree, both source and -bin Can app-office/openoffice-3.2.1 go stable? CVE-2010-0395 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-0395): OpenOffice.org 2.x and 3.0 before 3.2.1 allows user-assisted remote attackers to bypass Python macro security restrictions and execute arbitrary Python code via a crafted OpenDocument Text (ODT) file that triggers code execution when the macro directory structure is previewed. (In reply to comment #5) > Can app-office/openoffice-3.2.1 go stable? > In my view: Definitely. It still has some problems, but not more than any release before. Please note we should target 3.2.1-r1, as this has two more security fixes Stabilization is being handled in bug #345309, eh. With ppc being done, we are finally ready for the advisory Added to existing GLSA request. This issue was resolved and addressed in GLSA 201408-19 at http://security.gentoo.org/glsa/glsa-201408-19.xml by GLSA coordinator Kristian Fiskerstrand (K_F). |