Tor before 0.2.8.9 and 0.2.9.x before 0.2.9.4-alpha had internal functions that were entitled to expect that buf_t data had NUL termination, but the implementation of or/buffers.c did not ensure that NUL termination was present, which allows remote attackers to cause a denial of service (client, hidden service, relay, or authority crash) via crafted data.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://blog.torproject.org/blog/tor-0289-released-important-fixes | release notes vendor advisory |
https://github.com/torproject/tor/commit/3cea86eb2fbb65949673eb4ba8ebb695c87a57ce | patch vendor advisory |
https://security.gentoo.org/glsa/201612-45 | vendor advisory |
http://openwall.com/lists/oss-security/2016/10/19/11 | third party advisory mailing list |
https://trac.torproject.org/projects/tor/ticket/20384 | vendor advisory |
http://www.securityfocus.com/bid/95116 | vdb entry |
http://www.debian.org/security/2016/dsa-3694 | vendor advisory |