Updated tor packages fix security vulnerability

When checking for replays in the INTRODUCE1 cell data for a (legacy) onion service, Tor didn’t correctly detect replays in the RSA- encrypted part of the cell. It was previously checking for replays on the entire cell, but those can be circumvented due to the malleability of Tor’s legacy hybrid encryption. This can lead to a traffic confirmation attack (CVE-2017-8819). Denial of service issue where an attacker could crash a directory authority using a malformed router descriptor (CVE-2017-8820). Denial of service bug where an attacker could use a malformed directory object to cause a Tor instance to pause while OpenSSL would try to read a passphrase from the terminal (CVE-2017-8821). When running as a relay, Tor could build a path through itself, especially when it lost the version of its descriptor appearing in the consensus. When running as a relay, it could also choose itself as a guard (CVE-2017-8822). Use-after-free error that could crash v2 Tor onion services when they failed to open circuits while expiring introduction points (CVE-2017-8823).