Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 8 Sep 2015 13:02:44 +0530
From: Huzaifa Sidhpurwala <>
        Mitre CVE assign department <>
Subject: Pending CVE requests for glibc


I could not help but notice, some glibc security issues were not
assigned CVE ids.

1. glibc: multiple overflows in strxfrm()
Integer overflow when computing memory allocation sizes (similar to
CVE-2012-4412) was reported [1] in glibc strxfrm() function. Attached
strxfrm-int32.c should trigger this issue on a 32-bit systems.
Additionally, it was discovered [1] that strxfrm() falls back to an
unbounded alloca if malloc fails making it vulnerable to stack-based
buffer overflows (similar to CVE-2012-4424). Attached strxfrm-alloca.c
should trigger this issue.

Previously a request was made via:

2. glibc: _IO_wstr_overflow integer overflow
An integer overflow flaw, leading to a heap-based buffer overflow, was
found in glibc's _IO_wstr_overflow() function. If an application used
this function, it could cause the application to crash or, potentially,
execute arbitrary code with the privileges of the user running the

3. glibc: potential denial of service in internal_fnmatch()
It was reported [1] that when processing certain malformed patterns,
fnmatch can skip over the NUL byte terminating the pattern.  This can
potentially result in an application crash if fnmatch hits an unmapped
page before encountering a NUL byte.;h=4a28f4d55a6cc33474c0792fe93b5942d81bf185

Previously a request was made via:

4. glibc: potential denial of service in pop_fail_stack()
A crash was reported [1] during glibc extended regular expression
processing. No known patch exists at the time of writing.

Can MITRE please assign CVE ids to these flaws?


Huzaifa Sidhpurwala / Red Hat Product Security Team

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.