summaryrefslogtreecommitdiff
path: root/changes/bug20384
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-02-15 07:47:21 -0500
committerNick Mathewson <nickm@torproject.org>2017-02-15 07:47:21 -0500
commited806843dc8e7942a2a0abfbb2ae374e11963feb (patch)
tree3d3591b1db1c416661a74d9848794db8644b6146 /changes/bug20384
parent75fe218b166b4d4e46b50205104e9eeaa136e904 (diff)
parent3781f24b8014213c200f74973deb550382957a01 (diff)
downloadtor-ed806843dc8e7942a2a0abfbb2ae374e11963feb.tar.gz
tor-ed806843dc8e7942a2a0abfbb2ae374e11963feb.zip
Merge branch 'maint-0.2.6' into maint-0.2.7
Diffstat (limited to 'changes/bug20384')
-rw-r--r--changes/bug2038410
1 files changed, 10 insertions, 0 deletions
diff --git a/changes/bug20384 b/changes/bug20384
new file mode 100644
index 0000000000..591015ad94
--- /dev/null
+++ b/changes/bug20384
@@ -0,0 +1,10 @@
+ o Major features (security fixes):
+ - Prevent a class of security bugs caused by treating the contents
+ of a buffer chunk as if they were a NUL-terminated string. At
+ least one such bug seems to be present in all currently used
+ versions of Tor, and would allow an attacker to remotely crash
+ most Tor instances, especially those compiled with extra compiler
+ hardening. With this defense in place, such bugs can't crash Tor,
+ though we should still fix them as they occur. Closes ticket
+ 20384 (TROVE-2016-10-001).
+