Bug 1167503 - CVE-2014-3693 libreoffice: Use-After-Free in socket manager of Impress Remote [fedora-all]
Summary: CVE-2014-3693 libreoffice: Use-After-Free in socket manager of Impress Remote...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 20
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2014-3693
TreeView+ depends on / blocked
 
Reported: 2014-11-24 23:51 UTC by Murray McAllister
Modified: 2015-04-10 08:09 UTC (History)
6 users (show)

Fixed In Version: libreoffice-4.1.6.2-10.fc19
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-10 08:09:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Murray McAllister 2014-11-24 23:51:01 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

[bug automatically created by: add-tracking-bugs]

Comment 1 Murray McAllister 2014-11-24 23:51:09 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1164733,1167503

# Description of your update
notes=Security fix for CVE-2014-3693

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1164733,1167503

Comment 2 Caolan McNamara 2014-11-25 10:18:30 UTC
Current releases for Fedora 21+rawhide are at 4.3.4 and Fedora 20 is at 4.2.7 so are unaffected if up to date

Comment 3 Fedora Update System 2014-11-25 20:32:24 UTC
libreoffice-4.1.6.2-9.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libreoffice-4.1.6.2-9.fc19

Comment 4 Fedora Update System 2014-11-27 08:37:21 UTC
Package libreoffice-4.1.6.2-9.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-4.1.6.2-9.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15831/libreoffice-4.1.6.2-9.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-11-27 09:09:26 UTC
libreoffice-4.1.6.2-10.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libreoffice-4.1.6.2-10.fc19

Comment 7 pjp 2015-04-09 17:36:33 UTC
Hello caolanm,

You plan to fix this soon?

Comment 8 David Tardon 2015-04-10 08:09:07 UTC
It was fixed long ago. Just auto-close did not work for some reason.


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