public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/25812] Libio vtable protection is sometimes only partially enforced
Date: Fri, 22 Apr 2022 10:31:22 +0000	[thread overview]
Message-ID: <bug-25812-131-JY77LQFGOk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25812-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25812

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-
   Target Milestone|---                         |2.36
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for glibc 2.36 via:

commit 198abcbb94618730dae1b3f4393efaa49e0ec8c7
Author: Florian Weimer <fweimer@redhat.com>
Date:   Mon Apr 11 11:30:31 2022 +0200

    Default to --with-default-link=no (bug 25812)

    This is necessary to place the libio vtables into the RELRO segment.
    New tests elf/tst-relro-ldso and elf/tst-relro-libc are added to
    verify that this is what actually happens.

    The new tests fail on ia64 due to lack of (default) RELRO support
    inbutils, so they are XFAILed there.

I'm flagging this as security- because it is just a lack of intended hardening,
but not a vulnerability as such.

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

      parent reply	other threads:[~2022-04-22 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 17:22 [Bug stdio/25812] New: " maxkamper at outlook dot com
2020-04-15  7:09 ` [Bug stdio/25812] " luciham20 at gmail dot com
2020-04-15  7:11 ` luciham20 at gmail dot com
2021-09-30 13:57 ` fweimer at redhat dot com
2022-04-11  9:17 ` fweimer at redhat dot com
2022-04-12 11:27 ` fweimer at redhat dot com
2022-04-22 10:31 ` fweimer at redhat dot com [this message]

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-25812-131-JY77LQFGOk@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).