diff options
author | Mike DePaulo <mikedep333@gmail.com> | 2015-02-08 20:01:27 -0500 |
---|---|---|
committer | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | 2015-02-14 16:14:31 +0100 |
commit | 72790a55862f9a2232ba0cd7b072bbe3887cd820 (patch) | |
tree | 639d772385b19a0630c49a0b627ed68c4a784228 /nxcompshad/Logger.cpp | |
parent | df4a3b7270539843ae76275485ca76efcdf361d9 (diff) | |
download | nx-libs-72790a55862f9a2232ba0cd7b072bbe3887cd820.tar.gz nx-libs-72790a55862f9a2232ba0cd7b072bbe3887cd820.tar.bz2 nx-libs-72790a55862f9a2232ba0cd7b072bbe3887cd820.zip |
Avoid use-after-free in dix/dixfonts.c: doImageText() [CVE-2013-4396] from xorg/Xserver http://lists.x.org/archives/xorg-announce/2013-October/002332.html
Save a pointer to the passed in closure structure before copying it
and overwriting the *c pointer to point to our copy instead of the
original. If we hit an error, once we free(c), reset c to point to
the original structure before jumping to the cleanup code that
references *c.
Since one of the errors being checked for is whether the server was
able to malloc(c->nChars * itemSize), the client can potentially pass
a number of characters chosen to cause the malloc to fail and the
error path to be taken, resulting in the read from freed memory.
Since the memory is accessed almost immediately afterwards, and the
X server is mostly single threaded, the odds of the free memory having
invalid contents are low with most malloc implementations when not using
memory debugging features, but some allocators will definitely overwrite
the memory there, leading to a likely crash.
Diffstat (limited to 'nxcompshad/Logger.cpp')
0 files changed, 0 insertions, 0 deletions