public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sune Kloppenborg Jeppesen <jaervosz@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
	security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200609-01 ] Streamripper: Multiple remote buffer overflows
Date: Wed, 6 Sep 2006 16:52:30 +0200	[thread overview]
Message-ID: <200609061652.30770.jaervosz@gentoo.org> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200609-01
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: Streamripper: Multiple remote buffer overflows
      Date: September 06, 2006
      Bugs: #144861
        ID: 200609-01

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

Synopsis
========

Streamripper is vulnerable to multiple remote buffer overflows, leading
to the execution of arbitrary code.

Background
==========

Streamripper extracts and records individual MP3 file tracks from
SHOUTcast streams.

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

    -------------------------------------------------------------------
     Package                   /  Vulnerable  /             Unaffected
    -------------------------------------------------------------------
  1  media-sound/streamripper      < 1.61.26                >= 1.61.26

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

Ulf Harnhammar, from the Debian Security Audit Project, has found that
Streamripper is vulnerable to multiple stack based buffer overflows
caused by improper bounds checking when processing malformed HTTP
headers.

Impact
======

By enticing a user to connect to a malicious server, an attacker could
execute arbitrary code with the permissions of the user running
Streamripper

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Streamripper users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose ">=media-sound/streamripper-1.61.26"

References
==========

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

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

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

  http://security.gentoo.org/glsa/glsa-200609-01.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
http://bugs.gentoo.org.

License
=======

Copyright 2006 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: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2006-09-06 15: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=200609061652.30770.jaervosz@gentoo.org \
    --to=jaervosz@gentoo.org \
    --cc=bugtraq@securityfocus.com \
    --cc=full-disclosure@lists.grok.org.uk \
    --cc=gentoo-announce@lists.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