Showing posts with label SSL / TLS Connections. Show all posts
Showing posts with label SSL / TLS Connections. Show all posts

Wednesday, 23 September 2015

Apple Patches Critical Vulnerabilities In Apple Watch


Apple has released a new version of watchOS, the operating system for Apple Watch, in which a large number of vulnerabilities has been resolved. Through two of the patched vulnerabilities could execute a malicious website arbitrary code on the smart watch.

Also, various other vulnerabilities made the execution of arbitrary code as possible, for example, in the processing of a malignant font. Furthermore, there is a problem solved in apple pay making a payment terminal could figure out some recent transaction data on a payment. Also, it was for an attacker having a "privileged network position" is possible to intercept SSL / TLS connections and to monitor the activities of the user.

A vulnerability in the "Core Crypto" could allow an attacker to determine the RSA private key of the user. In total, Apple has watchOS two 37 vulnerabilities patched. Updating via the Software Update feature of the operating system.

Saturday, 28 March 2015

Researchers Reveal SSL Attack By 13-Year-Old RC4 Leak


Researchers have demonstrated an attack with which it is possible to be a part of the information that is to intercept encrypted via SSL / TLS. Unlike several other attacks on the encryption protocol is when attacked by security company Imperva ( pdf ) no need to sit through a man-in-the-middle attack between the user and the Internet. The passive eavesdropping of data, for example, would suffice received by a web application.

The attack is aimed at a thirteen year old vulnerability in the RC4 encryption algorithm, which is used in setting up an SSL / TLS connection. The vulnerability has already been described in 2001, and makes it possible to carry out a "plain text recovery attack" on SSL traffic as RC4 is the used encryption algorithm. Then an attacker can retrieve portions of session cookies, passwords and credit card numbers. The vulnerability is caused by the weak keys that uses RC4.

If an attacker enough SSL / TLS connections can be intercepted found such a weak key, which can then be read the first 100 bytes of the encrypted data. If an attacker tries to steal a session cookie can reduce the effective size of the cookie using this attack, which can be accelerated a brute force attack on the session cookie. Via session cookies, it is possible to take over the session of a user and so as to gain access to online accounts.

The problems with RC4 have long been known , and in 2013, Microsoft released an update for Windows to disable the algorithm. Most browsers would still support RC4, as well as more than half of the servers. According to the researchers such would be 30% of the TLS sessions are still using RC4, even if it is stronger AES algorithm available for quite some time.