From: Pierre-Yves Rofes <py@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200808-11 ] UUDeview: Insecure temporary file creation
Date: Mon, 11 Aug 2008 20:49:08 +0200 [thread overview]
Message-ID: <48A089A4.2090206@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3093 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200808-11
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: UUDeview: Insecure temporary file creation
Date: August 11, 2008
Bugs: #222275, #224193
ID: 200808-11
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability in UUDeview may allow local attackers to conduct
symlink attacks.
Background
==========
UUdeview is encoder and decoder supporting various binary formats.
NZBGet is a command-line based binary newsgrabber supporting .nzb
files.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 app-text/uudeview < 0.5.20-r1 >= 0.5.20-r1
2 news-nntp/nzbget < 0.4.0 >= 0.4.0
-------------------------------------------------------------------
2 affected packages on all of their supported architectures.
-------------------------------------------------------------------
Description
===========
UUdeview makes insecure usage of the tempnam() function when creating
temporary files. NZBGet includes a copy of the vulnerable code.
Impact
======
A local attacker could exploit this vulnerability to overwrite
arbitrary files on the system.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All UUDview users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-text/uudeview-0.5.20-r1"
All NZBget users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=news-nntp/nzbget-0.4.0"
References
==========
[ 1 ] CVE-2008-2266
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2266
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200808-11.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 2008 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: 260 bytes --]
reply other threads:[~2008-08-11 18:42 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=48A089A4.2090206@gentoo.org \
--to=py@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