public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201701-40 ] xdelta: User-assisted execution of arbitrary code
Date: Tue, 17 Jan 2017 12:41:27 +0900	[thread overview]
Message-ID: <52e27d0d-c312-c8c8-05b8-fe8be2652b62@gentoo.org> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2588 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201701-40
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: xdelta: User-assisted execution of arbitrary code
     Date: January 17, 2017
     Bugs: #574408
       ID: 201701-40

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

Synopsis
========

A buffer overflow in xdelta might allow remote attackers to execute
arbitrary code.

Background
==========

Xdelta is a C library and command-line tool for delta compression using
VCDIFF/RFC 3284 streams.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-util/xdelta              < 3.0.10                  >= 3.0.10 

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

A buffer overflow can be triggered within xdelta when ran against a
malicious input file.

Impact
======

A remote attacker could coerce the victim to run xdelta against a
malicious input file. This may be leveraged by an attacker to crash
xdelta and gain control of program execution.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All xdelta users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-util/xdelta-3.0.10"

References
==========

[ 1 ] CVE-2014-9765
      http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9765

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

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

 https://security.gentoo.org/glsa/201701-40

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 #1.1.2: Type: text/html, Size: 3699 bytes --]

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

                 reply	other threads:[~2017-01-17  3:51 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=52e27d0d-c312-c8c8-05b8-fe8be2652b62@gentoo.org \
    --to=bman@gentoo.org \
    --cc=gentoo-announce@lists.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