From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 18E73385B835; Fri, 10 Apr 2020 17:22:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 18E73385B835 From: "maxkamper at outlook dot com" To: glibc-bugs@sourceware.org Subject: [Bug stdio/25812] New: Libio vtable protection is sometimes only partially enforced Date: Fri, 10 Apr 2020 17:22:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: stdio X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maxkamper at outlook dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Apr 2020 17:22:28 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25812 Bug ID: 25812 Summary: Libio vtable protection is sometimes only partially enforced Product: glibc Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: stdio Assignee: unassigned at sourceware dot org Reporter: maxkamper at outlook dot com Target Milestone: --- Some versions of GLIBC bundled with popular distros still place their libio vtables in a writable segment. E.g. Ubuntu 1904 (which uses GLIBC 2.29) exhibits this behaviour, whilst the earlier Ubuntu 1804 (which uses GLIBC 2= .27) does not. This could be a choice on behalf of the distro maintainers but it seems unlikely. Vtable pointers are still checked before dereferencing but I feel this is undermined somewhat by the fact that the vtables themselves are mapped writable. Perhaps the issue is in the Makerules file, around line 549, which is comme= nted "If the linker is good enough, we can let it use its default linker script." The issue seems to manifest depending on the preceding ifeq statement's res= ult. I'm not well versed enough in the workings of linkers to comment as to why = this might be, but I've experienced the same writable vtable issue whilst buildi= ng GLIBC using more recent versions of GCC. --=20 You are receiving this mail because: You are on the CC list for the bug.=