summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2019-02-21 10:23:50 -0500
committerNick Mathewson <nickm@torproject.org>2019-02-21 10:23:50 -0500
commitc41fc1b2612746a478f503e80b0980db12a1cb19 (patch)
treec15ab9c34eb0e885516a18c4e5ccdc5aec1df549
parentebda5be9556f482067403b74cc8698eb1f0bafbe (diff)
downloadtor-c41fc1b2612746a478f503e80b0980db12a1cb19.tar.gz
tor-c41fc1b2612746a478f503e80b0980db12a1cb19.zip
Add TROVE-2019-001 to changelog for 0.3.4.11
-rw-r--r--ChangeLog14
-rw-r--r--changes/ticket291685
2 files changed, 13 insertions, 6 deletions
diff --git a/ChangeLog b/ChangeLog
index bffd08de8c..74d9b7ebf9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,17 @@
Changes in version 0.3.4.11 - 2019-02-21
- Tor 0.3.4.11 is the third stable release in its series.
+ Tor 0.3.4.11 is the third stable release in its series. It includes
+ a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
+ later. All Tor instances running an affected release should upgrade to
+ 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
+
+ o Major bugfixes (cell scheduler, KIST, security):
+ - Make KIST consider the outbuf length when computing what it can
+ put in the outbuf. Previously, KIST acted as though the outbuf
+ were empty, which could lead to the outbuf becoming too full. It
+ is possible that an attacker could exploit this bug to cause a Tor
+ client or relay to run out of memory and crash. Fixes bug 29168;
+ bugfix on 0.3.2.1-alpha. This issue is also being tracked as
+ TROVE-2019-001 and CVE-2019-8955.
o Minor features (geoip):
- Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
diff --git a/changes/ticket29168 b/changes/ticket29168
deleted file mode 100644
index 65c5232f65..0000000000
--- a/changes/ticket29168
+++ /dev/null
@@ -1,5 +0,0 @@
- o Major bugfixes (cell scheduler, KIST):
- - Make KIST to always take into account the outbuf length when computing
- what we can actually put in the outbuf. This could lead to the outbuf
- being filled up and thus a possible memory DoS vector. TROVE-2019-001.
- Fixes bug 29168; bugfix on 0.3.2.1-alpha.