From: Alex Legler <a3li@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 200909-08 ] C* music player: Insecure temporary file usage
Date: Wed, 9 Sep 2009 15:22:36 +0200 [thread overview]
Message-ID: <20090909152236.30c1ec41@neon> (raw)
[-- Attachment #1: Type: text/plain, Size: 2608 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200909-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: C* music player: Insecure temporary file usage
Date: September 09, 2009
Bugs: #250474
ID: 200909-08
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
An insecure temporary file usage has been reported in the C* music
player, allowing for symlink attacks.
Background
==========
The C* Music Player (cmus) is a modular and very configurable
ncurses-based audio player.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 media-sound/cmus < 2.2.0-r1 >= 2.2.0-r1
Description
===========
Dmitry E. Oboukhov reported that cmus-status-display does not handle
the "/tmp/cmus-status" temporary file securely.
Impact
======
A local attacker could perform symlink attacks to overwrite arbitrary
files with the privileges of the user running the application.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All C* music player users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose =media-sound/cmus-2.2.0-r1
References
==========
[ 1 ] CVE-2008-5375
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5375
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200909-08.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 2009 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: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2009-09-09 13:53 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=20090909152236.30c1ec41@neon \
--to=a3li@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