Bug 887416 (CVE-2012-5639) - CVE-2012-5639 LibreOffice / OpenOffice: automatic opening of embedded external data
Summary: CVE-2012-5639 LibreOffice / OpenOffice: automatic opening of embedded externa...
Status: NEW
Alias: CVE-2012-5639
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 887419 887420
Blocks: 887417
TreeView+ depends on / blocked
Reported: 2012-12-15 00:55 UTC by Kurt Seifried
Modified: 2019-09-29 12:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-12-16 14:05:26 UTC

Attachments (Terms of Use)

Description Kurt Seifried 2012-12-15 00:55:31 UTC
Timo Warns (Warns@Pre-Sense.DE) reported publicly that OpenOffice and
LibreOffice (as well as other Office Suites) fail to appropriately warn users
when a file with embedded content is opened. Additionally it is not possible
to disable the opening of embedded content within files. This can be used to
add tracking behavior to files or to deliver additional files that can
potentially exploit other security issues when parsed to the user.
Additionally if the file is converted (e.g. to a PDF) and then saved the
converted file may contain a direct copy of the embedded data, thus if
something sensitive if referenced (such as ~/.ssh/id_rsa) this information may
then be exposed if the resulting file is shared.

Comment 1 Kurt Seifried 2012-12-15 01:04:36 UTC
Created libreoffice tracking bugs for this issue

Affects: fedora-all [bug 887420]

Comment 2 Kurt Seifried 2012-12-15 01:04:39 UTC
Created openoffice.org tracking bugs for this issue

Affects: fedora-all [bug 887419]

Comment 4 Caolan McNamara 2012-12-18 11:35:23 UTC
We have various existing security options under tools->options->security->options and tools->options-security->macro security. It's plausible to e.g. extend these options with additional ones like "warn if saving files/creating pdfs if contents of externally linked data will be saved/printed to destination".

It's also plausible to attempt to map/follow the macro security concept of trusted sources and low to very high levels to some additional "only allow data to be automatically fetched from links" at low levels of security. Though IMO the default would probably have to be to allow links to at the very least the local filesystem by default for linked graphics, linked videos, master documents etc.

But its not particularly easy or quick to implement these. Especially if we want to be able to control access to local resources.

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