public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Behte <craig@gentoo.org>
To: gentoo-announce@gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
	 security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 201009-04 ] SARG: User-assisted execution of arbitrary code
Date: Tue, 07 Sep 2010 21:13:56 +0200	[thread overview]
Message-ID: <4C868EF4.2050400@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2714 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201009-04
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: SARG: User-assisted execution of arbitrary code
      Date: September 07, 2010
      Bugs: #222121
        ID: 201009-04

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

Synopsis
========

Multiple stack-based buffer overflow vulnerabilities were discovered in
SARG allowing for remote code execution.

Background
==========

SARG is the Squid Analysis Report Generator.

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

    -------------------------------------------------------------------
     Package            /  Vulnerable  /                    Unaffected
    -------------------------------------------------------------------
  1  net-analyzer/sarg     < 2.2.5-r5                      >= 2.2.5-r5

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

Multiple vulnerabilities were discovered in SARG. For further
information please consult the CVE entries referenced below.

Impact
======

These vulnerabilities might allow attackers to execute arbitrary code
via unknown vectors.

NOTE: This is a legacy GLSA. Updates for all affected architectures are
available since April 18, 2009. It is likely that your system is
already no longer affected by this issue.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All SARG users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=net-analyzer/sarg-2.2.5-r5"

References
==========

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

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

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

  http://security.gentoo.org/glsa/glsa-201009-04.xml

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 2010 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: 262 bytes --]

                 reply	other threads:[~2010-09-07 19:31 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=4C868EF4.2050400@gentoo.org \
    --to=craig@gentoo.org \
    --cc=bugtraq@securityfocus.com \
    --cc=full-disclosure@lists.grok.org.uk \
    --cc=gentoo-announce@gentoo.org \
    --cc=security-alerts@linuxsecurity.com \
    /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