aboutsummaryrefslogtreecommitdiffstats
path: root/.gitignore
diff options
context:
space:
mode:
authorKevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>2017-05-20 12:54:11 +0100
committerHauke Mehrtens <hauke@hauke-m.de>2017-05-21 23:56:17 +0200
commit6e10fc74fd569b71b6f64f5a2420dc624d73bee2 (patch)
treed8e72fa066288159ac702a5dd7aca2a0208ede83 /.gitignore
parentce7681d3289fd3befd20275aa54161f393bf561b (diff)
downloadupstream-6e10fc74fd569b71b6f64f5a2420dc624d73bee2.tar.gz
upstream-6e10fc74fd569b71b6f64f5a2420dc624d73bee2.tar.bz2
upstream-6e10fc74fd569b71b6f64f5a2420dc624d73bee2.zip
dropbear: bump to 2017.75
- 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. CVE-2017-9078 https://secure.ucc.asn.au/hg/dropbear/rev/c8114a48837c - 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. CVE-2017-9079 https://secure.ucc.asn.au/hg/dropbear/rev/0d889b068123 Refresh patches, rework 100-pubkey_path.patch to work with new authorized_keys validation. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions