From: Thierry Carrez <koon@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 200509-21 ] Hylafax: Insecure temporary file creation in xferfaxstats script
Date: Fri, 30 Sep 2005 15:02:11 +0200 [thread overview]
Message-ID: <433D3753.5000808@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2871 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200509-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: Hylafax: Insecure temporary file creation in xferfaxstats
script
Date: September 30, 2005
Bugs: #106882
ID: 200509-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Hylafax is vulnerable to linking attacks, potentially allowing a local
user to overwrite arbitrary files.
Background
==========
Hylafax is a client-server fax package for class 1 and 2 fax modems.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-misc/hylafax < 4.2.2 *>= 4.2.0-r3
*>= 4.2.1-r2
>= 4.2.2
Description
===========
Javier Fernandez-Sanguino has discovered that xferfaxstats cron script
supplied by Hylafax insecurely creates temporary files with predictable
filenames.
Impact
======
A local attacker could create symbolic links in the temporary file
directory, pointing to a valid file somewhere on the filesystem. When
the xferfaxstats script of Hylafax is executed, this would result in
the file being overwritten with the rights of the user running the
script, which typically is the root user.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Hylafax users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose net-misc/hylafax
References
==========
[ 1 ] Original bug report
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329384
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200509-21.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 2005 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.0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-09-30 13:14 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=433D3753.5000808@gentoo.org \
--to=koon@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