public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201703-01 ] OpenOffice: User-assisted execution of arbitrary code
Date: Sun, 19 Mar 2017 19:37:59 +0100	[thread overview]
Message-ID: <f84643e1-5d8b-5e75-989a-3e96b2125e5a@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2837 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201703-01
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: OpenOffice: User-assisted execution of arbitrary code
     Date: March 19, 2017
     Bugs: #597080
       ID: 201703-01

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

A vulnerability in OpenOffice Impress could cause memory corruption.

Background
==========

Apache OpenOffice is an open-source office software suite for word
processing, spreadsheets, presentations, graphics, databases and more.

Affected packages
=================

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  app-office/openoffice-bin
                                  < 4.1.3                    >= 4.1.3

Description
===========

An exploitable out-of-bounds vulnerability exists in OpenOffice Impress
when handling MetaActions.

Impact
======

A remote attacker could entice a user to open a specially crafted
OpenDocument Presentation .ODP or Presentation Template .OTP file using
OpenOffice Impress, possibly resulting in execution of arbitrary code
with the privileges of the process or a Denial of Service condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All OpenOffice users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot -v ">=app-office/openoffice-bin-4.1.3"

References
==========

[ 1 ] CVE-2016-1513
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1513
[ 2 ] TALOS-2016-0051
      http://www.talosintelligence.com/reports/TALOS-2016-0051/

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201703-01

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2017 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]

                 reply	other threads:[~2017-03-19 18:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f84643e1-5d8b-5e75-989a-3e96b2125e5a@gentoo.org \
    --to=whissi@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox