[Bug 211298] security/dropbear: update to 2016.74, set LICENSE

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Jul 22 16:21:27 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211298

            Bug ID: 211298
           Summary: security/dropbear: update to 2016.74, set LICENSE
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: pkubaj at anongoth.pl

Created attachment 172842
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172842&action=edit
2016.74

The patch attached updates the port to 2016.74 and sets the LICENSE. Note that
this release fixes some vulnerabilites:
- 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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list