Bug 2942 - libreoffice security issue: CVE-2011-2713
Summary: libreoffice security issue: CVE-2011-2713
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 1
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords: validated_update
: 2680 (view as bug list)
Depends on:
Blocks: 3672
  Show dependency treegraph
 
Reported: 2011-10-05 17:07 CEST by Nicolas Vigier
Modified: 2011-12-21 19:29 CET (History)
8 users (show)

See Also:
Source RPM: libreoffice
CVE:
Status comment:


Attachments
backtrace after segfault (10.10 KB, text/plain)
2011-12-09 04:14 CET, Dave Hodgins
Details
Spellcheck screenshot (73.44 KB, image/png)
2011-12-09 17:17 CET, claire robinson
Details

Description Nicolas Vigier 2011-10-05 17:07:02 CEST
Fixed in LibreOffice 3.4.3. I don't know if/where a patch is available.

http://www.libreoffice.org/advisories/CVE-2011-2713/
Manuel Hiebel 2011-10-05 18:05:23 CEST

Assignee: bugsquad => dmorganec

Comment 1 Nicolas Vigier 2011-10-06 01:10:32 CEST
There is some patches on redhat bugzilla :
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-2713

This is also fixed in version 3.3.4 (we are currently using 3.3.3.1), I think that's the version we should use as it seems to be a bugfix release.

More info in this announce :
http://lwn.net/Articles/461694/
Comment 2 D Morgan 2011-10-12 12:20:12 CEST
i would like, i need to look again because i have a compil issue with LO 3.3.4.
i will look after my vacations because i miss time now :)
Comment 3 D Morgan 2011-10-15 22:19:07 CEST
*** Bug 2680 has been marked as a duplicate of this bug. ***

CC: (none) => info

Comment 4 Manuel Hiebel 2011-11-11 01:35:24 CET
Ping ?
Comment 5 Christian Lohmaier 2011-11-18 00:03:15 CET
What compile issue? Folks on libreoffice's IRC-channel (#libreoffice-dev on freenode) and mailinglist (the developer's list is libreoffice@lists.freedesktop.org) surely would help solving that compile-bug...

Security fixes should have high priority and shall be considered major problems.

Priority: Normal => High
CC: (none) => lohmaier+mageia
Severity: normal => major

Comment 6 Florian Hubold 2011-12-01 20:30:11 CET
I'll try to take a look, as this is already 7 weeks late ...
FWIW, dmorgan has already commited 3.3.4.1 to updates/1 branch.

CC: (none) => doktor5000

Comment 7 D Morgan 2011-12-01 20:38:18 CET
in fact i am puzzled because i don't know what to do. 

Soon libreoffice 3.3 won't have any updates so what is the best to do ? fix our LO 3.3 or switch to LO 3.4 ?
Comment 8 D Morgan 2011-12-08 07:26:02 CET
libreoffice-3.3.4.1-1.1.mga1 is now available on updates_testing

Assignee: dmorganec => qa-bugs

Comment 9 David GEIGER 2011-12-08 17:53:37 CET
Tested libreoffice-3.3.4.1-1 on Mageia release 1 (Official) for x86_64 and for 
me it's Ok ,it work very fine.

Tested file :

-LibreOffice Writer : Ok
-LibreOffice Calc : Ok
-LibreOffice Impress : Ok
-LibreOffice Base : Ok

CC: (none) => geiger.david68210

Comment 10 Dave Hodgins 2011-12-08 20:59:40 CET
On i586, the installation is not clean.

/var/cache/urpmi/rpms/autocorr-cs-3.3.4.1-1.1.mga1.noarch.rpm: Invalid signature (NOT OK (no key): cannot open Packages database in )

I'm getting this on most (if not all) of the libreoffice packages.

CC: (none) => davidwhodgins

Comment 11 Dave Hodgins 2011-12-09 00:11:30 CET
I'm not sure if the problem in comment 10 was fixed on the mirrors, or
if it was fixed by my rebooting my system, switching to a cauldron
install, and then back, but the updates installed cleanly now.

I don't see a POC for CVE-2011-2713, so I'll just be testing that
everything seems to work ok on i586.
Comment 12 Manuel Hiebel 2011-12-09 00:32:43 CET
(In reply to comment #11)
> I'm not sure if the problem in comment 10 was fixed on the mirrors, or
> if it was fixed by my rebooting my system, switching to a cauldron
> install, and then back, but the updates installed cleanly now.
it was see http://svnweb.mageia.org/packages?view=revision&revision=179311
Comment 13 Dave Hodgins 2011-12-09 04:14:37 CET
Created attachment 1203 [details]
backtrace after segfault

I'm getting a segfault opening a document that was working before.
Comment 14 Dave Hodgins 2011-12-09 04:53:40 CET
It also segfaults with libreoffice-3.3.3.1-0.1.mga1.src.rpm, so
this is not a regression.

The document was written August 3rd, 2011, so the error has to
have been added since then.

All other documents I've opened have been ok.  Just chance that
I picked this one as the first one I tried.
Comment 15 D Morgan 2011-12-09 05:01:35 CET
can you open a bugreport for this segfault ? ( as this is not a regression this won't block this update, but will help when updating to LO 3.4.4 ) to see if this is fixed or not.

CC: (none) => dmorganec

Dave Hodgins 2011-12-09 05:34:42 CET

Blocks: (none) => 3672

Comment 16 Dave Hodgins 2011-12-09 05:36:52 CET
Bug 3672 opened for the segfault.

I'll continue testing other features for i586.
Comment 17 claire robinson 2011-12-09 16:51:02 CET
Mediawiki template defaults to German spell check at the bottom of the window. It doesn't actually seem to spell check anything though. This doesn't appear to be a regression from the current version.
Comment 18 claire robinson 2011-12-09 17:08:41 CET
In fact spell check doesn't seem to be working for me at all x86_64.
Comment 19 claire robinson 2011-12-09 17:17:59 CET
Created attachment 1208 [details]
Spellcheck screenshot

It is set to English (UK)
Comment 20 Dave Hodgins 2011-12-11 02:07:40 CET
Spell checking is working on the i586 system I'm using.  Haven't found any
other problems.  I've created a presentation, spreadsheet, database, etc.

I consider testing complete on i586.
Comment 21 claire robinson 2011-12-14 12:39:12 CET
$ rpm -qa | grep spell

Showed hunspell-en not installed x86_64 but it was on a working i586. myspell-en_GB was installed though.

When hunspell-en was installed libreoffice spellcheck and autocorrect works as it should.

There were no errors or any indication of a missing package. This can't be a regression but it should be looked at as spell checking is basic functionality for an office package.

There is no require on hunspell or the relevant language.

dmorgan do you want to look into this before it is pushed?
Comment 22 D Morgan 2011-12-18 23:16:34 CET
ok i look
Comment 23 D Morgan 2011-12-18 23:23:41 CET
a suggests on hunspell-en have been added ( new package on the BS )
Comment 24 claire robinson 2011-12-20 16:40:25 CET
Sorry dmorgan, in testing I don't notice any difference.

I don't want to delay the security update as it isn't a regression.

Should we push this and create a separate bug for the spell checking?
Comment 25 D Morgan 2011-12-20 16:43:22 CET
suggests are only handled at first install, this is why you don't see any difference. But yes please open a bugreport so we will be able to talk about this ( maybe a requires would be better )
Comment 26 claire robinson 2011-12-20 16:55:25 CET
Bug 3830 created for the spell checking issue.

Testing complete of the new build x86_64 other than that, requires testing i586 again.
Comment 27 D Morgan 2011-12-21 00:10:27 CET
why again testing on i586 ?
Comment 28 Dave Hodgins 2011-12-21 01:07:19 CET
(In reply to comment #27)
> why again testing on i586 ?

It's a new build.  Have to confirm the rpm packages have been signed
properly, etc.  The dependency on hunspell-en is a suggests rather
than a requires, so I don't think bug 2317 affects this, and the
depcheck script agrees.

Testing complete on i586.

Could someone from the sysadmin team push the srpm
libreoffice-3.3.4.1-1.3.mga1.src.rpm
from Core Updates Testing to Core Updates.

Advisory:  This security update for libreoffice corrects
CVE-2011-2713: Out of bounds property read in binary Microsoft Word (.doc) importer

https://bugs.mageia.org/show_bug.cgi?id=2942

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 29 Thomas Backlund 2011-12-21 19:29:22 CET
Update pushed.

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


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