public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15813] New: Multiple issues in __gen_tempname
Date: Fri, 02 Aug 2013 05:16:00 -0000	[thread overview]
Message-ID: <bug-15813-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15813

            Bug ID: 15813
           Summary: Multiple issues in __gen_tempname
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: bugdal at aerifal dot cx
                CC: drepper.fsp at gmail dot com

(1) Access to the static object value is unsynchronized, resulting in undefined
behavior. Undefined behavior is not desirable entropy.

(2) Low-resolution gettimeofday rather than high-resolution clock_gettime is
used as an entropy source.

(3) Entropy is only gathered once per run; subsequent attempts merely add 7777
to value, so that if an attacker can guess the initial temp name that will be
tried, the attacker can also guess all subsequent attempts for the same run.

Proposed solutions:

(1) Make value automatic. There is no value (pardon the pun) to keeping it
between runs.

(2) Use clock_gettime, possibly with multiple clocks (e.g. realtime and
cputime).

(3) Get new entropy on each attempt rather than adding the fixed value 7777.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-08-02  5:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  5:16 bugdal at aerifal dot cx [this message]
2013-10-11 21:25 ` [Bug libc/15813] " neleai at seznam dot cz
2013-10-11 21:29 ` bugdal at aerifal dot cx
2014-06-13 13:16 ` fweimer at redhat dot com
2020-09-09  9:37 ` jakub at redhat dot com
2020-09-09  9:51 ` jakub at redhat dot com
2020-09-09 12:19 ` adhemerval.zanella at linaro dot org
2020-09-09 12:35 ` kdudka at redhat dot com
2020-09-09 12:44 ` jakub at redhat dot com
2020-09-09 13:30 ` adhemerval.zanella at linaro dot org
2020-09-15 13:38 ` carlos at redhat dot com
2020-09-22 13:14 ` fweimer at redhat dot com
2020-09-22 13:15 ` fweimer at redhat dot com

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=bug-15813-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).