From: Charlotte Delenk <darkkirb@darkkirb.de>
To: musl@lists.openwall.com
Subject: Re: [musl] possible buffer overflow in crypt() -- musl-1.2.2
Date: Thu, 4 Nov 2021 17:32:37 +0100 [thread overview]
Message-ID: <20211104163237.4tjw7wopsg6oe7ow@nutty-noon> (raw)
In-Reply-To: <CAFvOk+oPyMJdhqavobK3DK5zhgY6puZkziDtUF4yqXkMwPQXZw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Hi,
On Thu, Nov 04, 2021 at 03:53:12PM +0100, Terefang Verigorn wrote:
> hello
>
> crypt.h declares
> ---
> struct crypt_data {
> int initialized;
> char __buf[256];
> };
> ---
>
> but crypt.c uses
> ---
> static char buf[128];
> return __crypt_r(key, salt, (struct crypt_data *)buf);
> ---
>
> the buf[128] should be rather buf[sizeof(crypt_data)]
It doesn't appear to be a potential buffer overflow issue. According to
the comment in __crypt_r, the crypt_data struct is only used as an
output buffer. The longest output appears to be around 80 bytes long
>
> --
> Terefang
--
Charlotte
https://keybase.io/darkkirb • GPG Key 3CEF5DDA915AECB0 • https://darkkirb.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2021-11-04 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 14:53 Terefang Verigorn
2021-11-04 15:13 ` [musl] " Terefang Verigorn
2021-11-04 16:13 ` [musl] " Rich Felker
2021-11-04 16:32 ` Charlotte Delenk [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=20211104163237.4tjw7wopsg6oe7ow@nutty-noon \
--to=darkkirb@darkkirb.de \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).