Makefile.am | 4 2 + 2 - 0 !
configure.ac | 3 0 + 3 - 0 !
2 files changed, 2 insertions(+), 5 deletions(-)

 do not consider webclients directory during build phase

Makefile.am | 6 1 + 5 - 0 !
configure.ac | 303 0 + 303 - 0 !
2 files changed, 1 insertion(+), 308 deletions(-)

 do not build x11vnc

test/encodingstest.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use format string argument with fprintf.

libvncclient/vncviewer.c | 20 19 + 1 - 0 !
1 file changed, 19 insertions(+), 1 deletion(-)

 fix integer overflow in mallocframebuffer() (cve-2014-6051)
 Promote integers to uint64_t to avoid integer overflow issue during
 frame buffer allocation for very large screen sizes

libvncclient/rfbproto.c | 10 7 + 3 - 0 !
libvncclient/vncviewer.c | 3 2 + 1 - 0 !
2 files changed, 9 insertions(+), 4 deletions(-)

  check for mallocframebuffer() return value (cve-2014-6052)
 If MallocFrameBuffer() returns FALSE, frame buffer pointer is left to
 NULL. Subsequent writes into that buffer could lead to memory
 corruption, or even arbitrary code execution.

libvncserver/rfbserver.c | 14 14 + 0 - 0 !
1 file changed, 14 insertions(+)

 do not accept a scaling factor of zero (cve-2014-6054)
 Do not accept a scaling factor of zero on
 PalmVNCSetScaleFactor and SetScale client->server messages. This would cause
 a division by zero and crash the server.

libvncserver/rfbserver.c | 57 44 + 13 - 0 !
1 file changed, 44 insertions(+), 13 deletions(-)

---

libvncserver/rfbserver.c | 5 5 + 0 - 0 !
1 file changed, 5 insertions(+)

 check malloc() return value (cve-2014-6053)
 Check malloc() return value on client->server ClientCutText
 message. Client can send up to 2**32-1 bytes of text, and such a large
 allocation is likely to fail in case of high memory pressure. This would in a
 server crash (write at address 0).