summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMatt Johnston <matt@ucc.asn.au>2016-07-21 23:04:24 +0800
committerMatt Johnston <matt@ucc.asn.au>2016-07-21 23:04:24 +0800
commit4732de71c673ed5e01b7a7be0c7fd18752868d0f (patch)
tree164b0bcaeaefd413c3a1a2c13d16b5c864888a2c /CHANGES
parent171456c6832ea7557ead828279f46438f1526626 (diff)
downloaddropbear-4732de71c673ed5e01b7a7be0c7fd18752868d0f.tar.gz
changelogs
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES32
1 files changed, 32 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index ceb01be..35d0427 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,35 @@
+2016.74 - 21 July 2016
+
+- Security: Message printout was vulnerable to format string injection.
+
+ If specific usernames including "%" symbols can be created on a system
+ (validated by getpwnam()) then an attacker could run arbitrary code as root
+ when connecting to Dropbear server.
+
+ A dbclient user who can control username or host arguments could potentially
+ run arbitrary code as the dbclient user. This could be a problem if scripts
+ or webpages pass untrusted input to the dbclient program.
+
+- Security: dropbearconvert import of OpenSSH keys could run arbitrary code as
+ the local dropbearconvert user when parsing malicious key files
+
+- Security: dbclient could run arbitrary code as the local dbclient user if
+ particular -m or -c arguments are provided. This could be an issue where
+ dbclient is used in scripts.
+
+- Security: dbclient or dropbear server could expose process memory to the
+ running user if compiled with DEBUG_TRACE and running with -v
+
+ The security issues were reported by an anonymous researcher working with
+ Beyond Security's SecuriTeam Secure Disclosure www.beyondsecurity.com/ssd.html
+
+- Fix port forwarding failure when connecting to domains that have both
+ IPv4 and IPv6 addresses.
+
+- Fix 100% CPU use while waiting for rekey to complete. Thanks to Zhang Hui P
+ for the patch
+
+
2016.73 - 18 March 2016
- Support syslog in dbclient, option -o usesyslog=yes. Patch from Konstantin Tokarev