diff options
author | Alan Coopersmith <alan.coopersmith@oracle.com> | 2013-03-02 11:44:19 -0800 |
---|---|---|
committer | Ulrich Sibiller <uli42@gmx.de> | 2016-10-12 09:34:38 +0200 |
commit | 0349af1145cb70985bc4cba2d439a7b50d6d95ea (patch) | |
tree | 73e067aafd3786777901ce99d41625405dd1aee9 /nxcomp/ProxyReadBuffer.h | |
parent | 8673bf0715160943da4937bac25cfeecd3e58b81 (diff) | |
download | nx-libs-0349af1145cb70985bc4cba2d439a7b50d6d95ea.tar.gz nx-libs-0349af1145cb70985bc4cba2d439a7b50d6d95ea.tar.bz2 nx-libs-0349af1145cb70985bc4cba2d439a7b50d6d95ea.zip |
Integer overflows in stringSectionSize() cause buffer overflow in ReadColornameDB() [CVE-2013-1981 6/13]
LoadColornameDB() calls stringSectionSize() to do a first pass over the
file (which may be provided by the user via XCMSDB environment variable)
to determine how much memory needs to be allocated to read in the file,
then allocates the returned sizes and calls ReadColornameDB() to load the
data from the file into that newly allocated memory.
If stringSectionSize() overflows the signed ints used to calculate the
file size (say if you have an xcmsdb with ~4 billion lines in or a
combined string length of ~4 gig - which while it may have been
inconceivable when Xlib was written, is quite possible today), then
LoadColornameDB() may allocate a memory buffer much smaller than the
amount of data ReadColornameDB() will write to it.
The total size is left limited to an int, because if your xcmsdb file
is larger than 2gb, you're doing it wrong.
Reported-by: Ilja Van Sprundel <ivansprundel@ioactive.com>
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Reviewed-by: Matthieu Herrb <matthieu.herrb@laas.fr>
Signed-off-by: Julien Cristau <jcristau@debian.org>
Backported-to-NX-by: Ulrich Sibiller <uli42@gmx.de>
Diffstat (limited to 'nxcomp/ProxyReadBuffer.h')
0 files changed, 0 insertions, 0 deletions