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 201607-13 ] libbsd: Arbitrary code execution
Date: Wed, 20 Jul 2016 20:21:21 +0900	[thread overview]
Message-ID: <80d10308-3641-49c5-c897-c9558161d4cb@gentoo.org> (raw)


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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201607-13
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: libbsd: Arbitrary code execution
     Date: July 20, 2016
     Bugs: #573160
       ID: 201607-13

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

Synopsis
========

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

Background
==========

This library provides useful functions commonly found on BSD systems,
and lacking on others like GNU systems, thus making it easier to port
projects with strong BSD origins, without needing to embed the same
code over and over again on each project.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-libs/libbsd              < 0.8.2                    >= 0.8.2 

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

libbsd contains a buffer overflow in the fgetwln() function. An if
statement, which is responsible for checking the necessity to
reallocate memory in the target buffer, is off by one therefore an out
of bounds write occurs.

Impact
======

Remote attackers could potentially execute arbitrary code with the
privileges of the process.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All libbsd users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --verbose --oneshot ">=dev-libs/libbsd-0.8.2"

References
==========

[ 1 ] CVE-2016-2090
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2090

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

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

 https://security.gentoo.org/glsa/201607-13

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 2016 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: 3849 bytes --]

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

                 reply	other threads:[~2016-07-20 11:25 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=80d10308-3641-49c5-c897-c9558161d4cb@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