summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMatt Johnston <matt@ucc.asn.au>2017-05-17 23:57:18 +0800
committerMatt Johnston <matt@ucc.asn.au>2017-05-17 23:57:18 +0800
commit5d2e3cf3fba3b63da40aab77333d391e19f756f1 (patch)
tree4fcf16c1d37ce76cc5fc83d070c39b531b532030 /CHANGES
parent1496ae874a833ba6f4e91b8ce4837c19a34b1170 (diff)
downloaddropbear-5d2e3cf3fba3b63da40aab77333d391e19f756f1.tar.gz
changes for 2017.75
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES25
1 files changed, 25 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index be4f9b7..c347c8a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,28 @@
+2017.75 - 18 May 2017
+
+- Security: Fix double-free in server TCP listener cleanup
+ A double-free in the server could be triggered by an authenticated user if
+ dropbear is running with -a (Allow connections to forwarded ports from any host)
+ This could potentially allow arbitrary code execution as root by an authenticated user.
+ Affects versions 2013.56 to 2016.74. Thanks to Mark Shepard for reporting the crash.
+
+- Security: Fix information disclosure with ~/.ssh/authorized_keys symlink.
+ Dropbear parsed authorized_keys as root, even if it were a symlink. The fix
+ is to switch to user permissions when opening authorized_keys
+
+ A user could symlink their ~/.ssh/authorized_keys to a root-owned file they
+ couldn't normally read. If they managed to get that file to contain valid
+ authorized_keys with command= options it might be possible to read other
+ contents of that file.
+ This information disclosure is to an already authenticated user.
+ Thanks to Jann Horn of Google Project Zero for reporting this.
+
+- Call fsync() to ensure that new hostkeys (dropbear -R) are flushed to disk
+ Thanks to Andrei Gherzan for a patch
+
+- Fix out of tree builds with bundled libtom
+ Thanks to Henrik Nordström and Peter Krefting for patches.
+
2016.74 - 21 July 2016
- Security: Message printout was vulnerable to format string injection.