summaryrefslogtreecommitdiff
path: root/print/py-PDF2
diff options
context:
space:
mode:
authorwiz <wiz@pkgsrc.org>2013-10-08 20:33:54 +0000
committerwiz <wiz@pkgsrc.org>2013-10-08 20:33:54 +0000
commit23c960f63827ff3a41a1628126ba2a5808aa189b (patch)
treef70ef5c6c118065dd135c50ca20f1c163af534a6 /print/py-PDF2
parent6342ae747a4b1649bd74fb7f43451f685f7c7e87 (diff)
downloadpkgsrc-23c960f63827ff3a41a1628126ba2a5808aa189b.tar.gz
Fix CVE-2013-4396.
From a4d9bf1259ad28f54b6d59a480b2009cc89ca623 Mon Sep 17 00:00:00 2001 From: Alan Coopersmith <alan.coopersmith@oracle.com> Date: Mon, 16 Sep 2013 21:47:16 -0700 Subject: [PATCH] Avoid use-after-free in dix/dixfonts.c: doImageText() 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. Reported-by: Pedro Ribeiro <pedrib@gmail.com> Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com> Reviewed-by: Julien Cristau <jcristau@debian.org> Bump PKGREVISION.
Diffstat (limited to 'print/py-PDF2')
0 files changed, 0 insertions, 0 deletions