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 201612-20 ] jq: Buffer overflow
Date: Thu, 8 Dec 2016 22:09:42 +0900	[thread overview]
Message-ID: <d75424c4-80ed-d48b-522e-cf30bc1e2500@gentoo.org> (raw)


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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201612-20
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: jq: Buffer overflow
     Date: December 08, 2016
     Bugs: #580606
       ID: 201612-20

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

Synopsis
========

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

Background
==========

jq is a lightweight and flexible command-line JSON processor.

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

    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  app-misc/jq                  < 1.5-r2                  >= 1.5-r2 

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

An off-by-one error was discovered in the tokenadd function in
jv_parse.c which triggers a heap-based buffer overflow.

Impact
======

A remote attacker could trick a victim into processing a specially
crafted JSON file, possibly resulting in the execution of arbitrary
code with the privileges of the process.  Additionally, a remote
attacker could cause a Denial of Service condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All jq users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=app-misc/jq-1.5-r2"

References
==========

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

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

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

 https://security.gentoo.org/glsa/201612-20

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: 3724 bytes --]

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

                 reply	other threads:[~2016-12-08 13:18 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=d75424c4-80ed-d48b-522e-cf30bc1e2500@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