[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-announce] [SECURITY] Buffer overrun in some uses of read-st
From: |
Peter Bex |
Subject: |
Re: [Chicken-announce] [SECURITY] Buffer overrun in some uses of read-string! procedure from "extras" |
Date: |
Fri, 27 Sep 2013 08:59:08 +0200 |
User-agent: |
Mutt/1.4.2.3i |
On Thu, Sep 26, 2013 at 09:02:16PM +0200, Peter Bex wrote:
> Hello CHICKEN users,
>
> A problem was found with the read-string! procedure from the "extras"
> unit, when used in a very particular way.
> [...]
> It turned out that there was a missing check for the situation when
> NUM was #f and the input size to be read from the port exceeded the
> given buffer's (STRING's) size. This will result in a buffer overrun,
> which may lead to general corruption of the stack or heap, and
> can potentially be used to execute arbitrary code.
This has been assigned CVE-2013-4385.
Kind regards,
The CHICKEN Team